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

Michael Clarke commented on JENKINS-13789:
------------------------------------------

One of the 'features' of CVS is that it doesn't support checking out by 
timestamp on a branch. To confuse things even more, it seems to accept the date 
parameter without any warning but then checks out the wrong thing. if 'use head 
if not found' (the -f parameter) is enabled then CVS ignores the date parameter 
unless it has switch to head which is why this seems to work in your second 
test.

The plugin was designed to handle this requirement but the logic has been coded 
wrongly. Should be easy enough to fix.
                
> 'cvs update' replaces the Tag file which has the branch name in it with a Tag 
> with time and date which effectively corresponds back to the Head
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13789
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13789
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>            Reporter: Amir Isfy
>            Assignee: Michael Clarke
>
> I am building a Module that comes from a CVS branch.
> 'cvs checkout' correctly keeps the branch name in the Tag file.
> Now after a clean checkout if the 'Use Update' is checked under 'Source Code 
> Management' then the command looks like:
> cvs update -d -P -r branch_name -D 15 May 2012 13:12:24 -0600 module_name
> After this the Tag file will have 'D2012.05.15.19.12.24' in it which 
> basically corresponds to the Head now.
> This could be related to this.
> Help please.

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