continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (CONTINUUM-576) all builds stuck in "in progress/scheduled" state
Date Mon, 13 Feb 2006 20:56:47 GMT
     [ http://jira.codehaus.org/browse/CONTINUUM-576?page=all ]
     
Emmanuel Venisse closed CONTINUUM-576:
--------------------------------------

     Assign To: Emmanuel Venisse
    Resolution: Fixed

I check if buildProcess is running without a child process( mvn, ant...).
If child process always running, i can't know its state (perhaps it's running or perhaps it's
blocked). If it's blocked, someone will need to kill manually the child process without restarting
Continuum.

> all builds stuck in "in progress/scheduled" state
> -------------------------------------------------
>
>          Key: CONTINUUM-576
>          URL: http://jira.codehaus.org/browse/CONTINUUM-576
>      Project: Continuum
>         Type: Bug

>   Components: Core system
>     Reporter: Brett Porter
>     Assignee: Emmanuel Venisse
>      Fix For: 1.0.3

>
>
> ci.codehaus.org was stuck in this state for about 20 days and noone noticed :)
> I know we have corrective measures on startup - is that something that can be done when
a build is triggered?
> Another option is to go all the way to detecting if the build process still exists, which
would allow the ability to implement "stop" functionality as well.

-- 
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


Mime
View raw message