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] Commented: (CONTINUUM-576) all builds stuck in "in progress/scheduled" state
Date Fri, 10 Feb 2006 20:31:48 GMT
    [ http://jira.codehaus.org/browse/CONTINUUM-576?page=comments#action_58396 ] 

Emmanuel Venisse commented on CONTINUUM-576:
--------------------------------------------

I can check if the child process (mvn, ant...) is running, if not, i can restore the status.
But i'll can't kill the child process because it can't work correctly on windows.

On windows, Process.destroy kill only cmd.bat that launch mvn or ant but not mvn or ant (http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4770092)

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