nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I ensure all jobs in a build are run on the same agent?

derekrosenzweig

Hello,

I have set up a Bamboo build plan that requires all jobs/stages to be run on the same physical machine (IE they depend on each other). When they are not, the builds fail. Is there any way to specify on a build-level that the jobs must run on the same physical machine? We use ELASTIC agents here, so we can't assume the hostname. I understand the Agent Matrix and Capabilities and all that, but this problem is not solved by specifying a capability since multiple instances of the ELASTIC agent will all have the same ones. Thanks!

Accepted answers

All comments

Mark de Bont_a8voxm

Defining a custom key/label for each agent (like: Hostname with the corresponding hostname) and then ensure the job has the requirement to run on a specific hostname?

Sergey Podobry _Stellarity Software_

Hi Derek,

Use tasks instead of jobs. They will be executed sequentially on the same agent.

Jason Edonick

Go to the agent you wish to pin the builds to
Add a custom capability similar to this:
image2016-8-18 10:49:13.png
Then, go to your build plan and add this to the requirements tab
image2016-8-18 10:50:19.png
You should be all set.

image2016-8-18 10:49:13.png

image2016-8-18 10:50:19.png

derekrosenzweig

I don't see a Requirements tab on my build plan.

derekrosenzweig

I see one on each job, and I already have some required capabilities defined. The problem with this method is that we use ELASTIC agents - they spin up/down as needed.

derekrosenzweig

The problem with this method is that we use ELASTIC agents - they spin up/down as needed and thus hostnames will never be the same at all times.

derekrosenzweig

I'm aware of how stages/jobs/tasks work, and I did consider refactoring everything into a single job, but there are fairly distinct stages. (A. lint the code and create a build artifact, B. run Chef provisioning to create a webserver, C. run the tests). C is dependent on B which is dependent on A.

Krystian Brazulewicz

The whole point of using Stages is ability to parallelize Job execution. By putting it all on the same agent you're serializing the whole flow so what's the point of creating stages? I think that Sergey's answer solves your problem.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bamboo