[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked
Title: Message Title Paavo Helde commented on JENKINS-17228 Re: Fail build when subversion workspace is locked We are currently using the "Install Hudson" workaround ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] [subversion-plugin] (JENKINS-17228) Fail build when subversion workspace is locked
Paavo Helde commented on JENKINS-17228 Fail build when subversion workspace is locked This issue is about when Jenkins has checked out and updating the working copy by itself. In this scenario every job should get its own workspace so concurrent access to it should not happen AFAIK. If there is concurrent access this probably means the svn checkout was not done by Jenkins; that would also explain why it does not attempt to wipe the workspace. Or have I misunderstood something here? Running concurrent builds in the same checkout folder seems not so good idea anyway. Jenkins provides an easy way to avoid that by setting the allowed number of executors to 1. 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.
[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked
Paavo Helde created JENKINS-17228 Fail build when subversion workspace is locked Issue Type: Improvement Assignee: Unassigned Components: subversion Created: 15/Mar/13 1:20 PM Description: This is a request to backport a Hudson fix into Jenkins. This is a 2-line change done in Hudson Subversion plugin 2.3.3, SHA 37ca9c134702878e6bb824dde108d63c6df043d8 https://github.com/hudson-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8 Rationale: subversion workspace often remains locked if previous svn update failed because of bad network connection, wiping the workspace is not useful for anything in this situation, rather the opposite. Project: Jenkins Labels: subversion Priority: Major Reporter: Paavo Helde 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/groups/opt_out.
[JIRA] (JENKINS-17228) Fail build when subversion workspace is locked
Paavo Helde commented on JENKINS-17228 Fail build when subversion workspace is locked In principle the workspace might also be locked because somebody else has logged into the slave computer and doing some svn operations manually. Therefore I would not suggest automatic "svn cleanup" or something like that, just failing the build (as the Hudson fix does) would be fine IMO. A user can always wipe the workspace explicitly if he/she is not able to solve the problem otherwise. 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/groups/opt_out.
