[
https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160759#comment-160759
]
Simon Strauch edited comment on JENKINS-12573 at 3/26/12 9:04 AM:
------------------------------------------------------------------
I have the same problem. Reason is, The CVS server don't understand "CEST",
"Central European Summer Time". I guess, this is caused by the CVS front end.
But a solution would be to use "+0200" instead of "CEST". The string "dd MMM
yyyy HH:mm:ss z" (lower case 'Z') in 'hudson.scm.CVSSCM'#'DATE_FORMATTER'
should solve the problem, too.
was (Author: 12delta):
I have the same problem. Reason is, The CVS server don't understand "CEST",
"Central European Summer Time". I guess, this is caused by the CVS front end.
But a solution would be to use "+0200" instead of "CEST". The string "dd MMM
yyyy HH:mm:ss z" (lower case 'Z') in 'hudson.scm.CVSSCM'#'DATE_FORMATTER'
should solve the problem.
> 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
