I would like to automate the migration of configuration changes from the Jira instance used for development (of Jira configuration changes, extensions etc.) to the Jira instance used to test the Jira changes, and finally deploy the changes to the production Jira.
Does anyone have experience, they would like to share, with any of the methods listed below? Does anyone have experience they would like to share with methods not listed below...? :-)
The particular question I would like to have answered, is: how do you handle changes in configurations between the different environments? The changes I need to do when moving configurations, are primarily the changing URLs to Confluence, Jenkins and Stash.
I have found these Jira plugins that both seem to be targeted to this use case:
Other possibilities are:
Regarding Configuration Manager for JIRA - You need to create projects only if you use the project snapshot deployment functionality and if you use system snapshot deployment then everything is created automatically (also, creating the synced projects when doing project snapshot deployment is a feature that we'll release soon).
Another important issue you might experience with the other methods you've listed is the automatic migration of issues when there are "incompatible" configuration changes like:
Configuration Manager for JIRA handles all described above, by providing migration UI for configuring how the migration should be appled and then updates all the issues accordingly on deployment.
One of the main scenarios that Configuration Manager for JIRA is targeted to is automating the Dev-Staging-Prouction deployment/migration process, so we'll be happy to make you a demo of the plugin and discuss your specific needs and also hear some feedback from you as it seems you've evaluated our product.
If you're interested just drop a mail to email@example.com.
Hi, thanks for your swift response!
Do you handle environment config changes? E.g. a different Confluence, Jenkins, Stash etc. for each of the environments for dev, staging and prod?
Or is this handled implicitly by manually setting these URLs in each of the environments, and then excluding the URL differences from the upgrade? If so: is that exclusion persisted so that it won't be presented as a diff on each config migration?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG