Can we determine the draft status in the pipeline?

[Jeremy Richardson]

For certain PR pipelines I'd like to not run them if the PR is marked as draft.

Is there a way to do this?

[Erik van der Schaaf]

Is there any chance of this becoming a feature? It would be the only reason for us to use the draft status.

[Nate Holland]

If you want to raise a feature request for this you can reach out here: https://support.atlassian.com/contact/?postauth=true#/

[Nate Holland]

Hi! I'm the engineer that oversaw the draft feature and we don't explicitly expose the draft status in the pipeline. As said above, you could make an API call inside your pipeline to check the draft status, but this wouldn't rebuild when the PR transitions from open to draft. So you would need to be careful about making sure builds re-run after the transition.

[Saxea _Flowie_]

You could call Bitbucket API inside the pipeline and check if draft is true, and then not proceed/exit in your pipeline script.

It would still trigger the pipeline though, and after you mark your PR as non-draft, you will likely want to build it. However, I haven't checked it, but it won't be trigger automatically, you will need to push to force a build of your PR.

We provide a Bitbucket Cloud app, Flowie, which you can configure it not trigger pipelines based on certain conditions of the PR. You can use Flowie's draft workflow feature based on labels to achieve what you want. An as soon as the conditions change, say you mark PR as non-draft it will trigger the build.

We don't support Bitbucket built in draft yet, as it was recently released, but it should be added soon, if you prefer it over Flowie's draft support.

[Marija Nikolova]

Hi @Saxea _Flowie_ @Nate Holland 

Is there any update on this feature? While it is possible to call the API and determine whether a pull request is in draft state from the pipeline script, having this information directly available in Bitbucket would help avoid unnecessary API calls and make workflows more sustainable.

One idea that we had is whether it would make sense for it to be integrated in the Events section of the Webhook configuration?

In our project, we are actively looking for ways to reduce the number of API calls between our CI/CD tooling and Bitbucket. Since we do not use Flowie, this functionality would be very helpful for us.

Thank you.

[Saxea _Flowie_]

Hi @Nate Holland

This feature request for Bitbucket is being tracked in BCLOUD-23649. 

Flowie now has support for Bitbucket built-in draft to trigger pipeline or use as conditions.