• Type: Improvement
• Resolution: Fixed
• Priority: Major
• Component/s: bitbucket-branch-source-plugin
• Labels:

  None

[JENKINS-72780] The key value for the build notification is an UUID which couldn't be filter in required build feature of Bitbucket

qiaofei created issue - 2024-02-29 06:31

qiaofei made changes - 2024-02-29 08:00

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches.   Could this function [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/blob/master/src/main/java/com/atlassian/bitbucket/jenkins/internal/status/BitbucketBuildStatusFactoryImpl.java#L40] return the branch value instead of GUID ID to make sure we could leverage the Bitbucket feature as well? !image-2024-02-29-14-29-28-725.png!

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here. [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/blob/master/src/main/java/com/atlassian/bitbucket/jenkins/internal/status/BitbucketBuildStatusFactoryImpl.java#L40]   !image-2024-02-29-14-29-28-725.png!

qiaofei made changes - 2024-02-29 08:01

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here. [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/blob/master/src/main/java/com/atlassian/bitbucket/jenkins/internal/status/BitbucketBuildStatusFactoryImpl.java#L40]   !image-2024-02-29-14-29-28-725.png!

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here. [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/blob/atlassian-bitbucket-server-integration-4.0.0/src/main/java/com/atlassian/bitbucket/jenkins/internal/status/BitbucketBuildStatusFactoryImpl.java#L40]     !image-2024-02-29-14-29-28-725.png!

qiaofei made changes - 2024-03-05 02:41

Component/s		New: bitbucket-branch-source-plugin [ 21428 ]
Component/s	Original: atlassian-bitbucket-server-integration-plugin [ 25721 ]
Description	Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here. [https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/blob/atlassian-bitbucket-server-integration-4.0.0/src/main/java/com/atlassian/bitbucket/jenkins/internal/status/BitbucketBuildStatusFactoryImpl.java#L40]     !image-2024-02-29-14-29-28-725.png!	New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here.  [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L201]       !image-2024-02-29-14-29-28-725.png!
Issue Type	Original: New Feature [ 2 ]	New: Bug [ 1 ]

qiaofei made changes - 2024-03-05 02:53

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] When using the bitbucket-server-integration-plugin with the latest version 4.0.0 , we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here.  [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L201]       !image-2024-02-29-14-29-28-725.png!

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here.  [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L201]       !image-2024-02-29-14-29-28-725.png!

qiaofei made changes - 2024-03-05 05:38

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is GUID ID. Then we couldn't use that to filter different branches. It seems this function returns the value of get the job name instead of the GUID name. But from the test result. The notification returns the GUID ID. Not sure what is going wrong here.  [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L201]       !image-2024-02-29-14-29-28-725.png!

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is Hash ID. Then we couldn't use that to filter different branches. [BitbucketBuildStatusNotifications.java#L201|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] [BitbucketBuildStatus.java#L95|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] Is it possible for this plugin to make the key value be more meanful and could be

qiaofei made changes - 2024-03-05 05:38

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is Hash ID. Then we couldn't use that to filter different branches. [BitbucketBuildStatusNotifications.java#L201|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] [BitbucketBuildStatus.java#L95|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] Is it possible for this plugin to make the key value be more meanful and could be

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is Hash ID. Then we couldn't use that to filter different branches. [BitbucketBuildStatusNotifications.java#L201|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] [BitbucketBuildStatus.java#L95|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] Is it possible for this plugin to make the key value be more meanful and could be filter by the Bitbucket required build feature?

qiaofei made changes - 2024-03-05 05:39

Description

Original: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is Hash ID. Then we couldn't use that to filter different branches. [BitbucketBuildStatusNotifications.java#L201|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] [BitbucketBuildStatus.java#L95|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] Is it possible for this plugin to make the key value be more meanful and could be filter by the Bitbucket required build feature?

New: There is a feature in Bitbucket that could filter the builds with key values. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] Environment： Plugin version |[Bitbucket Branch SourceVersion877.vb_b_d5243f6794|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source]| Jenkins version 2.405 we noticed the key value is Hash ID. Then we couldn't use that to filter different branches. [BitbucketBuildStatusNotifications.java#L201|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] [BitbucketBuildStatus.java#L95|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L95] Is it possible for this plugin to make the key value more meaningful and could be filtered by the Bitbucket required build feature?

qiaofei made changes - 2024-03-05 05:39

Attachment

Original: image-2024-02-29-14-29-28-725.png [ 62150 ]

Collapse comment: Jonathan Delizy added a comment - 2025-01-15 09:58

Jonathan Delizy added a comment - 2025-01-15 09:58

In current version (934.3.1), the key appears to be build from job name which is OK (https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/388049e52024761638ac1fd22fc5bb875e73ea75/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/impl/notifier/BitbucketBuildStatusNotifications.java#L269C27-L269C38)
but converted to a MD5 digest (https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/388049e52024761638ac1fd22fc5bb875e73ea75/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L121).

From my understanding of the API documentation, this should be a simple string.

Expand comment: Jonathan Delizy added a comment - 2025-01-15 09:58

Jonathan Delizy added a comment - 2025-01-15 09:58 In current version (934.3.1), the key appears to be build from job name which is OK ( https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/388049e52024761638ac1fd22fc5bb875e73ea75/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/impl/notifier/BitbucketBuildStatusNotifications.java#L269C27-L269C38 ) but converted to a MD5 digest ( https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/388049e52024761638ac1fd22fc5bb875e73ea75/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/api/BitbucketBuildStatus.java#L121 ). From my understanding of the API documentation , this should be a simple string.

Load more newer events