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

Bitbucket Server endless shows in-progress status if pull request is merged before build is finished

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • Jenkins 2.263.4
      Bitbucket Branch Source 2.9.11
      Atlassian Bitbucket v7.12.0

      Due to long Jenkins builds durations, we regularly decided zu merge a pull request, even if the running build is not finished yet.

      In that cases, the build status of the pull request in Bitbucket shows "in progress" for ever.

      This is confusing when the team audites the merged pull request.

       

      It seems, the build status in Bitbucket is not updated by the plugin any more, if the pull request is already merged there.

      But in Bitbucket, the merged pull request are still visible.

      Any opportunity to still update the build status to "failed" or "success" in this case?

          [JENKINS-66620] Bitbucket Server endless shows in-progress status if pull request is merged before build is finished

          Kalle Niemitalo added a comment - https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/472 would fix this in most cases.

          Nikolas Falco added a comment -

          Currently the PR would remain in the "In Progress" state, but since the PR is closed neither the build result nor the commit status have any impact on the workflow, otherwise I would expect you to have configured merge checks and conditions to prevent to merge if at least one build has passed.

          Teams would take care of the build status of the target branch. If the PR is reported as failed, in most cases the master result could be broken.

          Nikolas Falco added a comment - Currently the PR would remain in the "In Progress" state, but since the PR is closed neither the build result nor the commit status have any impact on the workflow, otherwise I would expect you to have configured merge checks and conditions to prevent to merge if at least one build has passed. Teams would take care of the build status of the target branch. If the PR is reported as failed, in most cases the master result could be broken.

            nfalco Nikolas Falco
            martinro martinro
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: