You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
First a little background.
We use bamboo jobs to deploy applications to an environment.
each of our environments consists of approx 25 different apps/services,etc that are all part of the Deploy to an environment.
We typically go from QA to Staging to production but also have a couple QA environments from testing different releases/diff. branches at the same time.
so today we have INT1 to QA1 to Staging for a release that goes out next week.
the release after is in QA2 so it would be INT2 to QA2 to Staging in a month from now roughly.
I have staging currently set to pull buildnumbers and some other artifacts from QA1. in 3-4 weeks I will need to switch all of those artifact pulls to get buildnumbers and other artifacts form QA2.
currently it takes me 30-40 minutes to change all those artifact pulls each time.
Is there a way to bulk change these? Do I need to do this with a sql script (which I dont prefer to do but can)?
I have other environments like staging that also have to pull from QA1 or QA2 depending on the release schedule and time.
We have configured these 25 deploys per env to have 2 different artifact pulls in the job. One is set to pull from QA1 the other is set to pull from QA2 but at any given time, only 1 of these is enabled and the other disabled.
I was able to see that the artifact task is actually defined and enabled in xml_definition_data.
Now have to find if there is a way to call an api to set that. doing this via sql is not going to be helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.