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

Can't Update Build Status With Bitbucket PR Builder Plugin On Latest Jenkins

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins v2.140 and v2.141, latest version of Bitbucket Pullrequest Builder Plugin, macOS Mojave
    • Similar Issues:

      Description

      I'm using this plugin https://wiki.jenkins.io/display/JENKINS/Bitbucket+pullrequest+builder+plugin as a build trigger, on Jenkins v2.140 and v2.141 it can't update the build status on Bitbucket when the build is finished (either success or failed). But on Jenkins v2.138, it is working just fine. After looking at the source code of that plugin, I believe the problem is related to this file https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/blob/master/src/main/java/bitbucketpullrequestbuilder/bitbucketpullrequestbuilder/BitbucketBuilds.java on line 41. On Jenkins v2.140 and v2.141 it seems that it the Jenkins Root URL is null, even though it is not, I already checked the Jenkins Root URL is indeed filled with valid URL. As this plugin is quite critical to my company, can you please take a look on what changed in the latest Jenkins that caused this issue?

        Attachments

          Activity

          Hide
          hugoduraes Hugo Durães added a comment -

          I'm experiencing the same issue.

          Show
          hugoduraes Hugo Durães added a comment - I'm experiencing the same issue.
          Hide
          _kaszpir_ Mochal Sochon added a comment - - edited

          You can even see the warning message on the screen you provided.

          Try changing `localhost` to `localhost.localdomain`, but for proper setup it should be FQDN.

          So this is not a plugin issue per se but jenkins misconfiguration.

          Show
          _kaszpir_ Mochal Sochon added a comment - - edited You can even see the warning message on the screen you provided. Try changing `localhost` to `localhost.localdomain`, but for proper setup it should be FQDN. So this is not a plugin issue per se but jenkins misconfiguration.

            People

            • Assignee:
              Unassigned
              Reporter:
              geraldi29 Geraldi Kusuma Arnanto
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: