Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61271

Disable build status notifications in Bitbucket Server Integration

XMLWordPrintable

    • Bitbucket Server Integration 3.2.0

      Please add a way to configure the Atlassian-maintained Bitbucket Server Integration plugin not to report any build status to Bitbucket Server.

      This is similar to JENKINS-49216 / JENKINS-49471 / JENKINS-36755 for Bitbucket Branch Source. There, the solution was to install Skip Notifications Trait Plugin and then add that trait to the branch sources. However, Bitbucket Server Integration does not seem to provide any withNotificationsDisabled method that Skip Notifications Trait could call. nor any other way to disable the notifications.

          [JENKINS-61271] Disable build status notifications in Bitbucket Server Integration

          Kalle Niemitalo created issue -
          Kalle Niemitalo made changes -
          Description Original: Please add a way to configure the Atlassian-maintained Bitbucket Server Integration plugin not to report any build status to Bitbucket Server.

          This is similar to JENKINS-49216 / JENKINS-49471 / JENKINS-36755 for [Bitbucket Branch Source|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/] There, the solution was to install [Skip Notifications Trait Plugin|https://plugins.jenkins.io/skip-notifications-trait/] and then add that trait to the branch sources. However, Bitbucket Server Integration does not seem to provide any {{withNotificationsDisabled}} method that Skip Notifications Trait could call. nor any other way to disable the notifications.           		New: Please add a way to configure the Atlassian-maintained Bitbucket Server Integration plugin not to report any build status to Bitbucket Server.

          This is similar to JENKINS-49216 / JENKINS-49471 / JENKINS-36755 for [Bitbucket Branch Source|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/]. There, the solution was to install [Skip Notifications Trait Plugin|https://plugins.jenkins.io/skip-notifications-trait/] and then add that trait to the branch sources. However, Bitbucket Server Integration does not seem to provide any {{withNotificationsDisabled}} method that Skip Notifications Trait could call. nor any other way to disable the notifications.
          Kalle Niemitalo made changes -
          Link New: This issue relates to JENKINS-36755 [ JENKINS-36755 ]
          Martin Henschke made changes -
          Assignee Original: Kristy Hughes [ khughes ]

          Martin Henschke added a comment -

          Hi Kalle, thanks for your suggestion.
          Because this is a core feature of the plugin, we don't have any plans to disable build statuses being sent to Bitbucket Server. If you're able, can you explain a little more about your use case, and why you don't want Jenkins sending build statuses to Bitbucket?
          Thanks,
          Martin

          Martin Henschke added a comment - Hi Kalle, thanks for your suggestion. Because this is a core feature of the plugin, we don't have any plans to disable build statuses being sent to Bitbucket Server. If you're able, can you explain a little more about your use case, and why you don't want Jenkins sending build statuses to Bitbucket? Thanks, Martin

          Kalle Niemitalo added a comment - - edited

          This would be for testing configuration changes or new plugin versions on a separate instance of Jenkins, without affecting whether Bitbucket Server considers pull requests OK to merge.

          Therefore, I would like to have this configurable in the Jenkins user interface (either per project, or for the entire Jenkins instance) or with a system property (for the Jenkins instance), rather than in a Jenkinsfile that would be read by the production Jenkins instance as well.

          Kalle Niemitalo added a comment - - edited This would be for testing configuration changes or new plugin versions on a separate instance of Jenkins, without affecting whether Bitbucket Server considers pull requests OK to merge. Therefore, I would like to have this configurable in the Jenkins user interface (either per project, or for the entire Jenkins instance) or with a system property (for the Jenkins instance), rather than in a Jenkinsfile that would be read by the production Jenkins instance as well.

          Valentin Delaye added a comment -

          Same use case here. Multiple instance (test/preprod) pointing to same jobdsl repository. We would like a way a skip notification.

          Valentin Delaye added a comment - Same use case here. Multiple instance (test/preprod) pointing to same jobdsl repository. We would like a way a skip notification.

          Kalle Niemitalo added a comment -

          PR #324 aims to implement this. I have not tested it.

          Kalle Niemitalo added a comment - PR #324 aims to implement this. I have not tested it.
          Kalle Niemitalo made changes -
          Remote Link New: This issue links to "JENKINS-61271 · Pull Request #324 · jenkinsci/atlassian-bitbucket-server-integration-plugin (Web Link)" [ 27430 ]

          Valentin Delaye added a comment -

          More than happy to manually test if I can download the .hpi somewhere (I guess there is no incremental builds for this plugin ?)

          Valentin Delaye added a comment - More than happy to manually test if I can download the .hpi somewhere (I guess there is no incremental builds for this plugin ?)

            Unassigned Unassigned
            kon Kalle Niemitalo
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: