Hudson is failing to calculate the changelog when the server has cvs 1.12.x installed.

Here is the Hudson's console output:

$ computing changelog
cvs [log aborted]: Can't parse date/time: `2010-10-17'
ERROR: cvs exited with error code 1
Command line was [Executing '/usr/bin/cvs' with arguments:
'-d:pserver:user@host:path'
'log'
'-S'
'-d'
'>=2010-10-17'
'module'

Going straight to the command line I can also reproduce this easilly by issuing:
$ CVS_PASSFILE=/opt/hudson/.cvspass /usr/bin/cvs -d:pserver:user@host:path log -S -d ">=2010-10-17" module
cvs [log aborted]: Can't parse date/time: `2010-10-17'

Now if I issue this command (notice that the date pattern changed)
$ CVS_PASSFILE=/opt/hudson/.cvspass /usr/bin/cvs -d:pserver:user@host:path log -S -d ">=2010-10-17 10:10" module
<normal output...>

From what've googled, seems like there are some differences on how dates are treated in CVS 1.11 and 1.12.

• "YYYY-MM-dd" works only in 1.11
• "YYYY-MM-dd HH:mm" works in 1.11 and 1.12.

So I guess we can change this pattern to something that works on both versions, I'm attaching a patch that does just that.

I found some nice commentaries about an issue just like this in Maven-SCM's JIRA, here's the link: http://jira.codehaus.org/browse/SCM-291

I must add that I'm already running a patched CVS plugin in my Hudson installation and it works just great. I hope you accept this patch because maintaining this would be terrible.