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

Alex Lehmann commented on JENKINS-12104:
----------------------------------------

I still have the problem in the 2.1 plugin, the files that are not in the 
branch are not picked up by rlog and the changes are not noticed

Building in workspace /home/lehmann/.jenkins/jobs/cvstest/workspace
cvs update -d -P -f -r BRANCHTEST workspace 
cvs update: Updating workspace
U workspace/branch1
U workspace/branch2
cvs rlog: Logging home/lehmann/cvstest
cvs rlog: warning: no revision `BRANCHTEST' in 
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in 
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in 
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
Finished: SUCCESS

(files named branch* are branched, files name file* are not)


                
> cvs-plugin doesn't catch file changes if the files are checked out with -f -r 
> (HEAD or branch)
> ----------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12104
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12104
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>         Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6
>            Reporter: Alex Lehmann
>            Assignee: Michael Clarke
>            Priority: Minor
>             Fix For: current
>
>
> When checking out a cvs repository with Branch and Use HEAD revision if tag 
> not found, the Changes list is always empty even though the build was 
> triggered by scm changes that are picked up the by cvs update in the build 
> log.
> Since the use Head function was introduced by me in 1.5, maybe the update 
> check is broken in a way I didn't notice, I will try to fix this.

--
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