[
https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160869#comment-160869
]
Alex Lehmann commented on JENKINS-12104:
----------------------------------------
{{monospaced}}
$ cvs rlog -d"14 Feb 2012 09:26:21 +0100<27 Mar 2012 12:00:00 +0100" -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
----------------------------
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
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'
{{monospaced}}
> 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
