[
https://issues.jenkins-ci.org/browse/JENKINS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158641#comment-158641
]
dogfood commented on JENKINS-753:
---------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs
#4|http://ci.jenkins-ci.org/job/plugins_cvs/4/]
[FIXED JENKINS-753] Allows performing a clean checkout if update fails
(Revision 794afd76127191e6a5174647d0c2620f0aadd915)
Result = SUCCESS
michael.m.clarke :
Files :
* src/main/java/hudson/scm/CVSSCM.java
* src/main/resources/hudson/scm/CVSSCM/config.jelly
> 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
>
> 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
