CI

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

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.

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.