Actions
Bug #17991
closedjenkins: Couldn't find any revision to build
Status:
Closed
Priority:
Normal
Assignee:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Updated by Loïc Dachary over 7 years ago
this happened right after a push --force
Updated by Alfredo Deza over 7 years ago
- Status changed from New to Closed
When a rebase happens that makes sha1s change (or disappear like in this case), then the build is expected to fail because the sha1 that triggered the job is nowhere to be
found anymore.
If this happens, it is OK to request a rebuild from a comment on Github like:
jenkins test this please
Updated by Loïc Dachary over 7 years ago
- Status changed from Closed to 15
This is a git plugin bug, close when it is fixed upstream. It needs to remain open so people know it is an active issue.
Updated by Alfredo Deza almost 7 years ago
- Status changed from 15 to Closed
This is a known problem for the Github Pull Requests plugin. Like I mentioned, the plugin can't figure out if there was a rebase and the commit is gone. If you want to keep track of this, please open a ticket against the plugin at https://github.com/janinko/ghprb
We can't provide any fixes for this.
Actions