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

When using Shared Libraries that use Bitbucket Server for the SCM, plugin fails to correctly post build status info

XMLWordPrintable

    • 3.4.1

      After a recent upgrade of Jenkins core and the BBS plugin from 2.1.3 to 3.2.2, we noticed that build status information was no longer being correctly shown on our internal Bitbucket Server instance - in the "/builds" section on on Bitbucket Server instance, the status shows "In Progress" indefinitely.

      The problem goes away if we manually go to /configure section of Jenkins, scroll down to the Global Pipeline Libraries area, and change the Retrieval Method/SCM from "Bitbucket Server" to "Git".

      (Context: most of our builds typically use Multibranch Pipelines)

      It appears as though the problem may be caused by build jobs that perform multiple checkouts as part of their build and is a regression in behavior from the older 2.1.3 version.

      To reiterate:

      • This problem doesn't occur when shared libraries aren't used on the master/controller with the 3.2.2 version, or if the "Git" retrieval method is used instead.
      • If we revert back to the 2.1.3 version, the problem goes away entirely, and shared libraries can be used with "Bitbucket Server" as the SCM retrieval method.

      Looking through the release notes from 2.1.3 to 3.2.2, I don't see anything that appears to explain this new change in behavior.

       

          [JENKINS-69268] When using Shared Libraries that use Bitbucket Server for the SCM, plugin fails to correctly post build status info

          Garen Parham created issue -
          Garen Parham made changes -
          Summary Original: When using Shared Libraries that use Bitbucket Server for the SCM, fails to correctly post build status info New: When using Shared Libraries that use Bitbucket Server for the SCM, plugin fails to correctly post build status info
          Atlassian Bitbucket Server made changes -
          Labels New: triaged
          Atlassian Bitbucket Server made changes -
          Assignee New: Atlassian Bitbucket Server [ atlassian_bbs ]
          Atlassian Bitbucket Server made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          David made changes -
          Assignee Original: Atlassian Bitbucket Server [ atlassian_bbs ] New: David [ djansons ]
          Garen Parham made changes -
          Description Original: After a recent upgrade of Jenkins core and the BBS plugin from {*}2.1.3 to 3.2.2{*}, we noticed that build status information was no longer being correctly shown on our internal Bitbucket Server instance - in the "/builds" section on on Bitbucket Server instance, the *status shows "In Progress" indefinitely.*

          The problem goes away if we manually go to /configure section of Jenkins, scroll down to the Global Pipeline Libraries area, and change the Retrieval Method/SCM from "Bitbucket Server" to "Git".

          (Context: most of our builds typically use Multibranch Pipelines)

          It appears as though the problem may be caused by build jobs that perform multiple checkouts as part of their build and is a regression in behavior from the older 2.1.3 version.

          To reiterate:
           * This problem doesn't occur when shared libraries aren't used on the master/controller with the 3.2.2 version, or if the "Git" retrieval method is used instead.
           * If we revert back to the 2.1.3 version, the problem goes away entirely, and shared libraries can be used with "Bitbucket Server" as the SCM retrieval method.

          Looking through the release notes from 3.0.0 to 3.2.2, I don't see anything that appears to explain this new change in behavior.

                      		New: After a recent upgrade of Jenkins core and the BBS plugin from {*}2.1.3 to 3.2.2{*}, we noticed that build status information was no longer being correctly shown on our internal Bitbucket Server instance - in the "/builds" section on on Bitbucket Server instance, the *status shows "In Progress" indefinitely.*

          The problem goes away if we manually go to /configure section of Jenkins, scroll down to the Global Pipeline Libraries area, and change the Retrieval Method/SCM from "Bitbucket Server" to "Git".

          (Context: most of our builds typically use Multibranch Pipelines)

          It appears as though the problem may be caused by build jobs that perform multiple checkouts as part of their build and is a regression in behavior from the older 2.1.3 version.

          To reiterate:
           * This problem doesn't occur when shared libraries aren't used on the master/controller with the 3.2.2 version, or if the "Git" retrieval method is used instead.
           * If we revert back to the 2.1.3 version, the problem goes away entirely, and shared libraries can be used with "Bitbucket Server" as the SCM retrieval method.

          Looking through the release notes from 2.1.3 to 3.2.2, I don't see anything that appears to explain this new change in behavior.

           
          David made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Fixed but Unreleased [ 10203 ]
          Martin Henschke made changes -
          Released As New: 3.4.0
          Josh Aguilar made changes -
          Released As Original: 3.4.0 New: 3.4.1
          Josh Aguilar made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Closed [ 6 ]

            djansons David
            garensel Garen Parham
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: