|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
7 years, and no activity beyond half-baked workarounds.
So.
From where I'm sat, there are two issues to resolve:
Importantly, building commits in precise order is irrelevant - you care whether given commits have been tested, not when they were tested. The order becomes especially irrelevant if you use the build name plugin to use commitid for build revision names, not an incrementing numeric value as is the default.
A bunch of this plumbing is already done - we can poll the SCM. Some SCM plugins clearly have knowledge of whether revisions have already been done or not (e.g. hudson/plugins/git/util/DefaultBuildChooser.java#L134). The less-implemented part is the first one - injecting the intermediate jobs into the build queue, not just the latest