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

Support optional custom Jenkins server URL value when registering a webhook

XMLWordPrintable

      After successful implementation of JENKINS-47891 (with https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/138) our Jenkins server can register the Native webhooks in repositories on a corporate Bitbucket Server.

      In our case however, the Jenkins server is accessible to Bitbucket under a different URL than is used by consumers in our development lab (and which it announces via generated URLs through the string in global Jenkins configuration settings), so we would like to have an option in the config of the Bitbucket connector for a particular server of using a non-default Jenkins URL for webhooks managed by that connector instance.

          [JENKINS-55423] Support optional custom Jenkins server URL value when registering a webhook

          Jim Klimov added a comment -

          https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/165

          Jim Klimov added a comment - https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/165

          Jim Klimov added a comment -

          PR merged, great thanks twz123 for the new webhook dialect support that my addition builds upon (JENKINS-47891), and to casz for reviewing my PR and making the initial code drop conform to the Java and Jenkins Plugin requirements.

          Jim Klimov added a comment - PR merged, great thanks twz123 for the new webhook dialect support that my addition builds upon ( JENKINS-47891 ), and to casz for reviewing my PR and making the initial code drop conform to the Java and Jenkins Plugin requirements.

          Jim Klimov added a comment -

          Now waiting for a release with this to appear.

          Jim Klimov added a comment - Now waiting for a release with this to appear.

            jimklimov Jim Klimov
            jimklimov Jim Klimov
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: