-
Bug
-
Resolution: Fixed
-
Critical
-
None
If I create a PR in github, the build automatically gets created.
However, if it fails, the next branch indexing log (which happened just after) does this:
Getting remote pull requests... Checking pull request #PR-4 Not mergeable, skipping
This removes the build entirely - so one cannot find out why it failed.
Incidentally, the "Not mergeable" isn't correct - it is mergeable, it's just Jenkins has reported a check-failure against it.
- is related to
-
JENKINS-33237 Failure to check out commit from a closed & reopened PR
-
- Resolved
-
-
JENKINS-33161 Allow merge commits to be built from origin PRs
-
- Resolved
-
- links to
[JENKINS-34120] Do not suppress unmergeable PRs
Component/s | Original: workflow-plugin [ 18820 ] | |
Assignee | Original: Jesse Glick [ jglick ] | |
Description |
Original:
If I create a PR in github, the build automatically gets created. However, if it fails, the next branch indexing log (which happened just after) does this: {{ Getting remote pull requests... Checking pull request #PR-4 Not mergeable, skipping}} This removes the build entirely - so one cannot find out why it failed. Incidentally, the "Not mergeable" isn't correct - it is mergeable, it's just Jenkins has reported a check-failure against it. |
New:
If I create a PR in github, the build automatically gets created. However, if it fails, the next branch indexing log (which happened just after) does this: {code:none} Getting remote pull requests... Checking pull request #PR-4 Not mergeable, skipping {code} This removes the build entirely - so one cannot find out why it failed. Incidentally, the "Not mergeable" isn't correct - it is mergeable, it's just Jenkins has reported a check-failure against it. |
Link |
New:
This issue is related to |
Summary | Original: PRs that fail builds immediately disappear from the build list | New: Do not suppress unmergeable PRs |
Assignee | New: Manuel Recena Soto [ recena ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Dubious. The stated error message indicates that GitHub considers the PR to not be mergeable without conflict. Has nothing to do with Jenkins build results.