We've run into an interesting conundrum with using Elastic Agents. We have two elastic images, one Linux, one Windows. Both images have a base set of capabilities in common (Maven versions, JDK and a few others). The issue we're having is that, if a plan defines a set of requirements that are only filled by the base capabilities (say only needs Maven) Bamboo won't be guaranteed to launch the Linux based image. This becomes a problem when the plan is actually expecting a Linux file system (a user script in the OOB script task for example). Is there a way to tell Bamboo to, in cases where a plans requirements could be met by more than one Elastic Image, to default to a specific image?
@edwin- Already thought of that, the problem is that we have 1000s of plans with multiple stages which would need to be updated with that value. We're currently dedicating plans that require Windows to the Windows based images but would like to get away from that as it adds a manual administration step to what is generally an automated self-service process for our end users.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events