Failures due to Jenkins only building latest commit when multiple pushed

[Code0x58]

If multiple commits are pushed to a branch in rapid succession, only the latest is built when Jenkins polls. The problem is GitLab will trigger pipelines for each of the commits, which will time out because the builds for them won't be automatically triggered.

I seem to recall the Jenkins build data included a list of commit hashes, so I think a solution would be to extend the loop that polls to find the build:

1. if no build was for the current commit, did any build contain the commit?
2. if so exit with return code 0 with a message to stderr to indicate what happened - GitLab does not yet have a neutral exit code (CE issue).

Is there a flag to make Jenkins build all intermediate commits? If so, the fix for this should include a flag to toggle this workaround or some way of detecting that it is needed.

p.s. there will still be timeouts when history is modified before a commit is discovered by Jenkins but that is a separate similar issue