We're using Git for source control, Bamboo for builds, Bamboo for deployments and Remedy ARS for change management.
I'm looking for automated trace-ability between the Remedy ARS Change Record and the Bamboo deployment to show which change record authorised deployment.
As we don't use JIRA for change records we cannot simply use the JIRA Bamboo integration.
Does anyone in the community have any working examples of a similar set-up with change records in a tool with no simple interface to bamboo yet providing automated trace-ability from deployment to change record?
In my case I'm having the script after I copy files to server. When I'm calling the service there are some bamboo variables that I pass to the API(artifact id, Version number and location). You can see the bamboo variables when the deployment project is running. The API collects info from change ticket and sends out email with the ticket number to the manager to approve the change request.
I think we can have the script to log the ticket number as well at the end or we can have some kind of message sent out in the form of JIRA comment. But since you're not using JIRA and if you want to just use bamboo, I think it has to be in log or some kind of commit back to your git repo with the ticket number.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot