![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git |
|
Created:
|
12/Dec/13 10:33 PM
|
|
Description:
|
Jenkins appears to obsess about knowing what the previous build's ref was. If that ref is unavailable in the current clone, the build fails.
This is prevalent in builds triggered by gerrit, since they will often be from random refs in the history, and not necessarily in any meaningful order.
It would be nice if there was a way to tell Jenkins to not even try to determine what the previous build was, but meanwhile it would just help if the build didn't fall over just because the previous build is unavailable.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Christian Goetze
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
