|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15160) earliest git hash pa... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)
- [JIRA] (JENKINS-15160) earliest git ha... [email protected] (JIRA)

Ideally, there would be a checkbox for the user to indicate whether s/he wants every commit built, or just the latest commit built. In my case, job B runs many times slower than job A. If every commit is built, it would take days for job B to catch up. That would mean I would need to manually kill some runs in job B to help it catching up. constant manual intervention is very undesirable.