[
https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160761#comment-160761
]
Simon Strauch edited comment on JENKINS-12573 at 3/26/12 9:25 AM:
------------------------------------------------------------------
Our local CVS client understand "+0200", but it don't understand '-D
"2012-03-26 11:10 CEST"'. Well, that is the "cvs" command-line-tool, I not sure
how the Jenkins CVS client works. Would it be a solution to eliminate the
timezone problem with an UTC/GMT timestamp? E.g. '-D "2012-03-26 09:10 GMT"'
instead of '-D "2012-03-26 11:10 CEST"'.
was (Author: 12delta):
Our local CVS client understand "+0200", but it don't understand '-D
"2012-03-26 11:10 CEST"'. Well, that is the "cvs" command-line-tool. Would it
be a solution to eliminate the timezone problem with an UTC/GMT timestamp? E.g.
'-D "2012-03-26 09:10 GMT"' instead of '-D "2012-03-26 11:10 CEST"'.
> CVS plugin version 2.0 checkout failed: Can't parse date/time
> -------------------------------------------------------------
>
> Key: JENKINS-12573
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12573
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Environment: Jenkins ver. 1.424.2
> Jenkins CVS Plug-in 2.0
> Reporter: Eric Co
> Assignee: Michael Clarke
>
> After I upgraded the CVS plugin 2.0, got the following error:
> cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc
> cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT
--
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
