• Type: Bug
• Resolution: Unresolved
• Priority: Trivial
• Component/s: bitbucket-branch-source-plugin
• Labels:

  None
• Environment:

  Jenkins 2.263.4
  Bitbucket Branch Source 2.9.11
  Atlassian Bitbucket v7.12.0

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

martinro created issue - 2021-09-13 08:42

martinro made changes - 2021-09-13 08:45

Description

Original: 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 is not updated by the plugin any more if the pull request is already merged. 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?

New: 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?

Collapse comment: Kalle Niemitalo added a comment - 2021-09-13 11:37

Kalle Niemitalo added a comment - 2021-09-13 11:37

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

Expand comment: Kalle Niemitalo added a comment - 2021-09-13 11:37

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

Nikolas Falco made changes - 2024-11-08 03:10

Assignee

New: Nikolas Falco [ nfalco ]

Collapse comment: Nikolas Falco added a comment - 2024-12-02 10:48

Nikolas Falco added a comment - 2024-12-02 10:48

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.

Expand comment: Nikolas Falco added a comment - 2024-12-02 10:48

Nikolas Falco added a comment - 2024-12-02 10:48 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 made changes - 2024-12-02 10:48

Priority

Original: Minor [ 4 ]

New: Trivial [ 5 ]

Nikolas Falco made changes - 2025-01-27 16:53

Resolution		New: Won't Do [ 10001 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Nikolas Falco made changes - 2025-01-27 16:53

Resolution	Original: Won't Do [ 10001 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]