Closed KageRiyuu closed 2 years ago
Thanks @KageRiyuu! Waiting for review here https://github.com/bitrise-io/bitrise-steplib/pull/3284
Merged. You should be able to use the new version directly from Bitrise now.
@KageRiyuu we're facing some issues with this change. See #6
I think using the workflowId should fix this while still supporting your use-case: https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status/pull/7
Could you try this patch and see if it works for you?
You should be able to try this version by editing your bitrise.yml file directly in the web editor on bitrise.io:
Instead of
- bitrise-step-bitbucket-server-post-build-status@0.0:
inputs: ...
You would use:
- git::https://github.com/teameh/bitrise-step-bitbucket-server-post-build-status.git@key_based_on_workflow:
inputs:
Does that work?
Key for per build status should be unique, https://developer.atlassian.com/server/bitbucket/how-tos/updating-build-status-for-commits/#multiple-builds
Currently if you build a branch and PR for that branch both post build status to same commit with Key "Bitrise", so they override each other. Also on Build tab on Bitbucket (or using get API) it displays only one build status.