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

Log when the auto registration of webhook fails for BB cloud

XMLWordPrintable

      "auto-register webhooks" for BB cloud requires admin permission, thats clear - but it took my a long time until I realized that my user was not having the required permissions.

      Even tough I checked the box "Auto-register webhook", I had no evidence that there was any attempt of really do so. No error, no message.

      It would be good if the user would get some sort of a hint that this operation did not work as expected.

          [JENKINS-39897] Log when the auto registration of webhook fails for BB cloud

          Dominik Bartholdi created issue -
          James Dumay made changes -
          Labels New: technical-debt
          James Dumay made changes -
          Issue Type Original: Improvement [ 4 ] New: Bug [ 1 ]

          Evin Callahan added a comment - - edited

          I believe I'm also seeing this issue, as I don't see webhooks registered in any of the repositories that the branch source plugin properly scans and clones. I can see build notifications working from jenkins->bitbucket which makes me believe it has the connectivity it needs to the bitbucket api.

          I'm not sure where I would see a failure for this - is there a specific log file or event or time that the webhooks should be created where I can provide additional logs or understand further what's going on?

          One other thing - I keep seeing in documentation that we need to have the post webhook plugin installed in bitbucket ( ie in this link here), however that's not available for bitbucket cloud. Is that still required? Other documents mention that it's ONLY supported on bitbucket cloud.

          Running on Jenkins 2.73 and cloudbees-bitbucket-branch-source:2.2.3

          Evin Callahan added a comment - - edited I believe I'm also seeing this issue, as I don't see webhooks registered in any of the repositories that the branch source plugin properly scans and clones. I can see build notifications working from jenkins->bitbucket which makes me believe it has the connectivity it needs to the bitbucket api. I'm not sure where I would see a failure for this - is there a specific log file or event or time that the webhooks should be created where I can provide additional logs or understand further what's going on? One other thing - I keep seeing in documentation that we need to have the post webhook plugin installed in bitbucket ( ie in this link here ), however that's not available for bitbucket cloud. Is that still required? Other documents mention that it's ONLY supported on bitbucket cloud. Running on Jenkins 2.73 and cloudbees-bitbucket-branch-source:2.2.3
          Andrew Bayer made changes -
          Labels Original: technical-debt New: technical-debt triaged-2018-11
          Nikolas Falco made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Nikolas Falco made changes -
          Assignee Original: Antonio Muñiz [ amuniz ] New: Nikolas Falco [ nfalco ]
          Nikolas Falco made changes -
          Summary Original: auto-register of webhook silently fails for BB cloud New: Log when the auto registration of webhook fails for BB cloud

          Nikolas Falco added a comment -

          Actually error about webhook are in the jenkins log.
          Webhook registration is async is not possible log in the console log or in the "scan the organization folder/multibranch project" log because the listener is not available.

          Nikolas Falco added a comment - Actually error about webhook are in the jenkins log. Webhook registration is async is not possible log in the console log or in the "scan the organization folder/multibranch project" log because the listener is not available.
          Nikolas Falco made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            nfalco Nikolas Falco
            imod Dominik Bartholdi
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: