![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
subversion-plugin |
|
Created:
|
10/Apr/15 8:15 PM
|
|
Description:
|
The Jenkins job/build immediately fails if the working copy is locked. For me, this is undesirable due to the structure of our repository. We have multiple builds trying to update their individual portions of the working copy. Unfortunately, svn locks the working copy one directory above the one in which the update occurs, so we get failures if multiple builds are triggered concurrently, even though they are in different sections of the repository. The way it currently works, we are notifying commiters that they have a build failure even though the changes themselves did not cause the failure, and then if they have nothing more to commit there is no choice but to MANUALLY trigger the job again.
I would much prefer to have this be configurable. Let me decide if I want it to fail (current behavior), or try again every ___ seconds with ___ total attempts, other...
|
|
Environment:
|
Windows Server 2012 R2
Jenkins v1.573
Subversion Plug-in v2.5
Chrome
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tim Bradt
|
|
|
|
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.
