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

Failing to report build status to BitBucket server

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Trivial
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins 2.149
      bitbucket-branch-source-plugin 2.2.13
      Windows Server 2008
    • Similar Issues:

      Description

      I updated to version 2.2.13 today and found that builds are failing to report to BitBucket. Neither in-progress or a complete result is posted. Reverting back to 2.2.12 fixes the issue for me.

      When it fails I see this in the console output

      [Bitbucket] Notifying pull request build result
      Can not determine Jenkins root URL or Jenkins URL is not a valid URL regarding Bitbucket API. Commit status notifications are disabled until a root URL is configured in Jenkins global configuration.

      I don't see this now that I reverted

        Attachments

          Activity

          Hide
          sherve Samuel Hervé added a comment -

          Same issue here, also had to revert back to version 2.2.12

          Could this be related to https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/131 or https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/146 ?

          Show
          sherve Samuel Hervé added a comment - Same issue here, also had to revert back to version 2.2.12 Could this be related to https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/131 or https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/146 ?
          Hide
          geoff Geoff Dunn added a comment -

          You're spot on Samuel Hervé. https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/146 contains the error message that I saw and added conditions that could throw that exception.

          Show
          geoff Geoff Dunn added a comment - You're spot on Samuel Hervé . https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/146  contains the error message that I saw and added conditions that could throw that exception.
          Hide
          casz Joseph Petersen added a comment - - edited

          Definitely not a bug, this is the intended error message you should handle as Jenkins admins.

          Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server requirements.
          Perhaps the error message could be improved?

          Show
          casz Joseph Petersen added a comment - - edited Definitely not a bug, this is the intended error message you should handle as Jenkins admins. Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server requirements. Perhaps the error message could be improved?
          Hide
          sherve Samuel Hervé added a comment -

          Setting a FQDN as Jenkins URL fixed it indeed. It used to work with a non-FQDN hostname at plugin version 2.2.12 though (maybe by accident ?), a better error message would help for sure.

          Show
          sherve Samuel Hervé added a comment - Setting a FQDN as Jenkins URL fixed it indeed. It used to work with a non-FQDN hostname at plugin version 2.2.12 though (maybe by accident ?), a better error message would help for sure.
          Hide
          casz Joseph Petersen added a comment -

          Depends on the version of Bitbucket server your using  New version limits the build status API to FQDN hostnames.

          Show
          casz Joseph Petersen added a comment - Depends on the version of Bitbucket server your using  New version limits the build status API to FQDN hostnames.
          Hide
          sherve Samuel Hervé added a comment -

          Good to know, thank you for the clarification !

          Show
          sherve Samuel Hervé added a comment - Good to know, thank you for the clarification !
          Hide
          chrismaes Chris Maes added a comment - - edited

          I observe the exact same error with version 2.2.15. Reverting to 2.2.12 solved the problem

          updating to 2.2.15 again and specifying a FQDN also solved the problem

          Show
          chrismaes Chris Maes added a comment - - edited I observe the exact same error with version 2.2.15. Reverting to 2.2.12 solved the problem updating to 2.2.15 again and specifying a FQDN also solved the problem

            People

            • Assignee:
              Unassigned
              Reporter:
              geoff Geoff Dunn
            • Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: