[
http://jira.codehaus.org/browse/CONTINUUM-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106271
]
Julien S commented on CONTINUUM-1384:
-------------------------------------
Indeed, I've been testing with beta-2 with a similar setup for a couple of
days, and was about to comment that the issue seems to be fixed for us in
beta-2 too. Thank you for the fix.
> Build error when enqueing happens during SCM update
> ---------------------------------------------------
>
> Key: CONTINUUM-1384
> URL: http://jira.codehaus.org/browse/CONTINUUM-1384
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1-beta-1
> Reporter: Julien S
> Assignee: Emmanuel Venisse
> Fix For: 1.1-beta-3
>
>
> I've noticed on several occasions that a project is suddenly marked as
> "Error" without any change on the project itself.
> The error is displayed on the global summary and in the project group
> summary, but it does not appear on the builds page of the project.
> There is no error in the logs.
> As it happens quite often, I've finally noticed that the "trigger" to this
> issue seem to be the following:
> When a schedule runs to enqueue project while one of them is being updated
> from its SCM (even when there is no change), the project is then marked as
> error as described above.
> More specifically, it seems that the log pattern common to these build
> failure is:
> 377162928 [pool-1-thread-1] INFO
> org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/bash -c
> "cd /drive/continuum-1.1-beta-1/work/55 && cvs -z3 -f -q update -d"
> 377162928 [pool-1-thread-1] INFO
> org.apache.maven.scm.manager.ScmManager:default - Working directory:
> /drive/continuum-1.1-beta-1/work/55
> 377163028 [defaultScheduler_Worker-1] INFO
> org.apache.maven.continuum.build.settings.SchedulesActivator:default -
> >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 377163307 [pool-1-thread-1] INFO
> org.apache.maven.continuum.buildcontroller.BuildController:default - Merging
> SCM results
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
