[ https://issues.jenkins-ci.org/browse/JENKINS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Clarke resolved JENKINS-753. ------------------------------------ Fix Version/s: current Resolution: Fixed Feature added in 2.1 to provide the user with a checkbox to enable cleaning workspace on failed update > Should perform clean checkout if update fails > --------------------------------------------- > > Key: JENKINS-753 > URL: https://issues.jenkins-ci.org/browse/JENKINS-753 > Project: Jenkins > Issue Type: Bug > Components: cvs > Affects Versions: current > Environment: Platform: All, OS: All > Reporter: jglick > Assignee: Michael Clarke > Fix For: current > > > In a project configured to use CVS update mode, and doing incremental builds > (or > faulty clean steps), it can happen that CVS updates produce conflicts. For > example, on occasion what was previously a .cvsignore'd build product becomes > checked into the repository - say, ANTLR-generated files if you no longer wish > to depend on antlr.jar for regular builds. In such cases, "cvs up" fails and > the > build breaks. There is no way to correct the build from the admin GUI, either; > you need to log in to the server and delete the workspace. > If a project is configured to use update mode, and the update command fails, I > think Hudson should automatically attempt a clean checkout, in the interests > of > robustness and zero maintenance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira