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; } } }

Bamboo build merged two builds in one

Luiz Saggioro

I have a bamboo plan set to 'Bitbucket Server repository triggered' and 'Branches' set to manual. My repo is configured with 'master' as being the branch and 'Enable quiet period' is not checked.

Essentially, this plan runs whenever there is a merge to master and everything works fine.

Although, I observed the following behaviour:

Branch A merges into master -> Triggers build 1

(while build 1 is running)

Branch B merges into master -> nothing appeared on the bamboo queue

Branch C merges into master -> nothing appeared on the bamboo queue

(build 1 finishes)

Build 2 starts with changes from both merges (Branch B -> master and Branch C -> master)

It doesn't seem right, since 'quiet period' is not enabled. My train of thought is that 1 change triggers 1 build.

Is it the intended behaviour or is it a bug? Maybe there is another option on bamboo to change this behaviour that I'm not aware of.

Edit 1: I'm using version 6.6.2 build 60606 - 14 Aug 18

Accepted answers

All comments

Foong

Is the Concurrent build enabled at Administration > Plans > Concurrent builds ?

If not, Branch B merges will fail to trigger a new build.

Luiz Saggioro

No, it's not enabled.

Foong

Does it work fine after enabled?

Luiz Saggioro

Sorry for the late reply.

My pipeline needs to be serial, so I cannot enable Concurrent builds without breaking it.

I can think of enabling Concurrent builds and limiting one agent per plan, so that I'll never have parallel builds, but would still have a build queue, but it's not scalable.

Is there any other solution to that?

Tom Emerson

We add a unique capability for each Build Agent. For build jobs that must be serial, a specific, unique capability requirement is added. This breaks redundancy, should that now special build agent fail, manual intervention required to resume the pipeline.

A solution, but not optimum.

Welcome!

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

Quick Links

Find more posts tagged with

bamboo