Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.
Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.
Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.
Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.
You can however make your build statuses more actionable from within Bitbucket by setting up a [merge check| for minimum successful builds which will restrict merges to PRs with a successful build against them.[https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html]] for minimum successful builds which will restrict merges to PRs with a successful build against them.
Yes, I was imagining a "Jenkins" user and sending API requests on behalf of that user. It will look like the butler himself has marked the PR as "Needs Work" LOL.