Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.3
-
Fix Version/s: 1.1-alpha-1
-
Component/s: SCM
-
Labels:None
-
Environment:Win2003 SP1, Maven 2.0.4
-
Complexity:Intermediate
-
Number of attachments :
Description
it seems to be a problem with the local provider. The local provider doesn't initialize the change
date because we can't know it and in DefaultContinuumScm, we check it. Please create an issue.
Emmanuel
thorsten@online.de a écrit :
> Hi,
>
> now i have five projects, that start at 12:00.
> All Projects get this error (see below).
>
> (Manuell starting works fine - scm provider is 'file')
>
> What is going wrong?
>
>
> Thanks,
> Thorsten
>
>
>
> Build statistics:
> State: Error
> Previous State: Ok
> Started at: Fr, 14 Jul 2006 12:00:51 +0200
> Finished at: Fr, 14 Jul 2006 12:01:05 +0200
> Total time: 14s
> Build Trigger: Schedule
> Exit code: 0
> Building machine hostname: srv-ew-web
> Operating system : Windows 2003(Service Pack 1)
> Java version : 1.5.0_06(Sun Microsystems Inc.)
>
>
> ****************************************************************************
> Build Error:
> ****************************************************************************
> org.apache.maven.continuum.scm.ContinuumScmException: Cannot checkout sources.
> at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:276)
> at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58)
> at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166)
> at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47)
> at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.continuum.scm.DefaultContinuumScm.convertScmResult(DefaultContinuumScm.java:414)
> at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:244)
> ... 5 more
>
>
>
Occasionally some of our builds are failing during scheduled builds. Forced builds are working fine. I see the same stacktrace as above.
A difference is that not all builds are failing, and the problems do not occur every time.
I'm using Continuum 1.0.3, but I've updated maven-scm-api and maven-scm-provider-local (snapshot version maven-scm-provider-local-1.0-20060616.154545-4.jar).
(originally discussed on http://www.nabble.com/Occassional-NPEs-while-checking-out-through-scm-local-in-scheduled-build-tf2289437.html)