[ 
https://issues.jenkins-ci.org/browse/JENKINS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158639#comment-158639
 ] 

SCM/JIRA link daemon commented on JENKINS-753:
----------------------------------------------

Code changed in jenkins
User: Michael Clarke
Path:
 src/main/java/hudson/scm/CVSSCM.java
http://jenkins-ci.org/commit/cvs-plugin/1ccef67edc26350d544b2ae5ebfebed5ed91ac8c
Log:
  [JENKINS-12599] Changing how password is set in connections so as not to
modify port numbers (as per comments #2 and #3)
[JENKINS-753] Stop processing if update fails and we're not going to do
a workspace clean


Compare: https://github.com/jenkinsci/cvs-plugin/compare/39da798...1ccef67


                
> 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

        

Reply via email to