I may have found another bug with cvs. We currently manage our differing builds by Tagging the platform in CVS. For example, our stage build is everything that has the Stage tag on it. While setting up a build for a given tag I got the exception at the end of this message. I think that it is failing while trying to compute the change log. Is this a possibility? I am still on version
1.75. I turned on logging of CVS using the script interface and it didn't really give more information. Anything else I should look for?
started
[STAGE-Build] $ cvs -t -z9 -d :pserver:user@xxxxxxxxxxx
:/cvs/aoma co -r STAGE -d workspace -D Wednesday, January 31, 2007 1:15:12 AM UTC moduleName
cvs checkout: notice: main loop with CVSROOT=:pserver:user@xxxxxxxxxxx:/cvs/moduleName
... snip ...
FATAL: No such directory exists. Did you specify the correct branch?: /apps/hudson/jobs/STAGE-Build/workspace
java.io.IOException: No such directory exists. Did you specify the correct branch?: /apps/hudson/jobs/STAGE-Build/workspace
at hudson.scm.CVSSCM.archive(CVSSCM.java:281)
at hudson.scm.CVSSCM.access$200(CVSSCM.java:85)
at hudson.scm.CVSSCM$1.invoke(CVSSCM.java:198)
at hudson.scm.CVSSCM$1.invoke(CVSSCM.java:193)
at hudson.FilePath.act
(FilePath.java:191)
at hudson.scm.CVSSCM.checkout(CVSSCM.java:193)
at hudson.model.AbstractProject.checkout(AbstractProject.java:250)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:103)
at hudson.model.Run.run(Run.java:533)
at hudson.model.Build.run(Build.java:203)
at hudson.model.Executor.run(Executor.java:61)
| 