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

Disable build status notifications in Bitbucket Server Integration

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            mhenschke_atlassian 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

            Show
            mhenschke_atlassian 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
            Hide
            kon 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.

            Show
            kon 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.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              kon Kalle Niemitalo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: