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

Pipelines with manual steps are shown as paused

Pete Smith_gjs5q4

Hi all.

I'm hoping this hasn't been asked and I've just missed it.

Since about last Friday, one of our repos in bitbucket has been building very strangely.

The repos has 3 automatic steps - unit tests, smoke test and simulator build.

Once these have passed, we can then build a range of steps manually, to produce an installation pack for each of our customers.

Up to about last Friday, the build would be marked as passed so long as those first 3 automatic steps passed.

Since Friday (ish, I'm not entirely sure when), any pipeline which has ever run, and had the first 3 steps passed is now shown as "Paused".

We have some pipelines on that repos which have no additional steps (used to push artifacts to our internal registry). When these pass, they go green.

Has there recently been any updates to Bitbucket, or do you think someone has been fiddling with some settings somewhere and retrospectively changed the behaviour of pipelines?

If anyone can give me any pointers, I'd greatly appreciated it.

Thanks in advance.

Pete

Accepted answers

Theodora Boudale

Hi everyone,

Our Product Manager, Edmund Munday, has addressed another community question regarding this topic. You can read a detailed explanation here:

https://community.atlassian.com/t5/Bitbucket-questions/Why-do-I-see-the-completed-pipeline-status-as-quot-Paused-quot/qaq-p/2695645#M104654

To summarize, the "Paused" status now more accurately represents the build's actual state in the system. This adjustment is purely cosmetic and aims to enhance consistency and transparency within the user interface. It specifically impacts Pipelines that include manual steps. Such a trigger is commonly employed for manually approving deployments or managing optional steps that may be executed toward the end of a pipeline.

It's important to note that these pipelines have always been designated as "Paused" within the system, a detail consistently reflected in the user interface when sorting pipelines by their status.

If you have any more questions, please don't hesitate to let us know.

Kind regards,
Theodora

All comments

Daniel Baber

I am seeing the same thing with a project. Haven't seen the normal "Successful" but stop behavior since.... well it looks like all of the runs in the past got this status now.

Pete Smith_gjs5q4

Hi.

Thanks, that's useful to know it's not just me then!

Hopefully someone at Atlassian will sort it out.

Thanks again.

Marin_znoqiu

Same issue here and I hope this is just a bug and not intended behavior, as it is a huge and confusing change in the UX of our pipelines.

Theodora Boudale

Hi everyone,

Our Product Manager, Edmund Munday, has addressed another community question regarding this topic. You can read a detailed explanation here:

https://community.atlassian.com/t5/Bitbucket-questions/Why-do-I-see-the-completed-pipeline-status-as-quot-Paused-quot/qaq-p/2695645#M104654

It's important to note that these pipelines have always been designated as "Paused" within the system, a detail consistently reflected in the user interface when sorting pipelines by their status.

If you have any more questions, please don't hesitate to let us know.

Kind regards,
Theodora

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

pipelines