Yeah, it would be beneficial to have the ability to specify an agent to run entire plan for a branch.
We have a job in later stage that have dependency configured in earlier stage, so if another agent tries to run it, it will fail.
For now, I have to move the tasks in dependent job into the earlier job, so they run together.

The single biggest reason for separating the stages is so that a single stage failure doesn't require rebuilding the entire plan.  This feature would be extremely helpful for my organization as we have dozens of plans which could run concurrently and as some of them use the same repositories, can lead to building the wrong commit (ie: 'Revision' doesn't match the latest 'Commit' in the code commits); very irritating.

Seems like a no-brainer here; checkbox "Agent treats entire plans as a single stage" or something similar.

Thanks Rahul.

May be it solves, but it would be great that, along with the agent capabilities with respect to plan, the option that agent is locked for the complete plan is required. Since my problem is when two agents map to a single plan they may take turns to run Stages in build plan which is not what I need. What I need is an Agent once started to run build plan should be the one to complete it and not other agent can interfere with the running plan even if its capability matches.

Thanks,
Rahul

Hi Rahul,

If we implemented BAM-3491 would that solve this issue for you?

Thanks
James

Perfect, an option for locking agent for the build plan should resolve are problem. Please have that created.

Thanks

Make sense...

Say, would it be OK if I'd update the summary of this ticket to be "add option in Bamboo to lock the agent for the complete build"? I think it would better reflect what can be done in Bamboo and other people could vote on such issue. What do you think? Good/bad idea?

Thanks and that is what I have done as a solution to put everything in a single stage. I had to put the cleanup tasks in different stage so that multiple agents could clean up and start various environments in parallel but the build has to run only after all clean up is done hence the next stage. We have several environments to clean up, as in Apache Felix, Jackrabbit, maven repository etc..and wanted to clean all in parallel. In future we may have cleanup to be done in cloud environment on multiple nodes hence the requirement for parallel cleanup.

I would suggest to have an option to lock the agent for the complete build. As we are using repository isolation and hence switching agents during build stages does not seem to be good option.

Ah, and as a side note - why don't you merge all your stages into one single stage/job?
Seems to me that a single Job containing all your tasks:

• Clean History tasks
• Clean Repository tasks
• Clean Cache tasks
• Build and Test tasks
• Report Results tasks

...would work better - after all, why do you need to split these steps? To have parallel cleaning up (Clean History + Clean Repository + Clean Cache), or just to have better visually organized the build tasks in your Plan?

Hello Rahul,

While definitely it's not a bug (what you experience is the designed behavior of the Bamboo - we might argue whether the design is correct, but what you describe is the expected execution from the current Bamboo design point of view), I do agree that for your use-case Bamboo is working improperly and it would be nice if Bamboo would have some Plan locking or priority mechanisms built-in.

However, can I ask you to check if the BAM-3705 issue is actually what you need in Bamboo? Because if it is, then I'd like to close this issue here and ask you to watch&vote the BAM-3705 instead. What would you say?

regards,
Piotr Stefaniak
Bamboo developer