Our software needs to be built on a dedicated agent based on the software version ( below version X, build on agent A, above version X, build on agent B). The "easy" approach would be to create 2 plans with the 2 requirements sets and simply invoke the appropriate plan based on the version we are trying to build. The problem with this approach is that there are now 2 plans ( with 4 stages and a lot of jobs) duplicated : 3 stages are similar and only 1 job differs in one stage. My main concern with this is the space taken by the checkouts on the agents.
Is there a way to "programmatically" update a job requirement ( that would be done in the first stage first job and be used at stage 2) ?
This approach is probably frowned upon, but with firefox and the firebug plugin you can see the POST calls being made when you manipulate settings in the web UI. You can make those same calls from the command line or script using curl (I'm assuming linux). This is not a great solution since the URLs used in the Bamboo web UI are not public and can change from version to version.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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