continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bannij (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1747) Double builds
Date Wed, 06 Aug 2008 12:50:26 GMT


Michael Bannij commented on CONTINUUM-1747:

Just found that we have exactly the same behaviour. I think this is somehow connected to the
next bug: CONTINUUM-1511.

> Double builds
> -------------
>                 Key: CONTINUUM-1747
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Michael Johns
>             Fix For: 1.x
> We're using Continuum 1.1 with Maven 2.0.8 on a Windows 2003 Server box, and we've just
> experiencing a very maddening problem.  Every time a build is scheduled to fire, it appears
> to fire twice.  It always fails the first time with the following error:
> {code}
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(
>         at
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(
>         at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$
>         at$
>         at
>         at$Worker.runTask(
>         at$
>         at
> Caused by: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error
> mapping metadata:add.project.artifact.not.found.error
> add.project.unknown.error
>         at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(
>         at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(
>         ... 8 more
> {code}
> The second build proceeds properly, but emails are always triggered due to the change
in status
> from error to success.  Interestingly enough, we don't get mails when that first build
> which changes the status from success to error.
> This happens with every single one of our projects, and it just started happening recently.
>  We used Continuum 1.1 for a few months with no troubles.  If you look at the build history
> for a project, every other build is about 12 seconds and ends in failure.  And then another
> build fires immediately after it and works fine.
> I'd like to delete the projects and re-add them, but there's a Continuum bug (CONTINUUM-1630)
> that prevents me from doing so.  I am 99% positive this has nothing to do with our build
> either.  We don't have very many, and they are fairly standard looking.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message