Bug report: PRs are (sometimes) linked to an incorrect Jenkins job build.
We have put PR validation in place using Jenkins (LTS 2.164.3) and the Bitbucket PR Builder plugin (v1.4.30). Each PR is checked by a number of different Jenkins jobs.
What happens, however, is that the PR links to the incorrect Jenkins build.
Example
For example, we have a PR 109. On that PR, there is a note on the builds saying “1 of 3 passed”:
When clicking on that, a popup shows up with references to 3 Jenkins builds:
Bug report: PRs are (sometimes) linked to an incorrect Jenkins job build.
We have put PR validation in place using Jenkins (LTS 2.164.3) and the Bitbucket PR Builder plugin (v1.4.30). Each PR is checked by a number of different Jenkins jobs.
What happens, however, is that the PR links to the incorrect Jenkins build.
Example For example, we have a PR 109. On that PR, there is a note on the builds saying “1 of 3 passed”:
When clicking on that, a popup shows up with references to 3 Jenkins builds:
The links have the following targets:
Note that none of the 3 links is appropriate: