You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/07/30 19:25:52 UTC

[jira] [Resolved] (MESOS-554) Jenkins scheduler should properly handle TASK_LOST

     [ https://issues.apache.org/jira/browse/MESOS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone resolved MESOS-554.
------------------------------

    Resolution: Won't Fix

Launching a Jenkins slave doesn't necessarily mean Jenkins would relaunch a failed job on the new slave. This should ideally be handled by job level semantics (e.g, retry on failure, though i don't know if jenkins supports this out of the box).
                
> Jenkins scheduler should properly handle TASK_LOST
> --------------------------------------------------
>
>                 Key: MESOS-554
>                 URL: https://issues.apache.org/jira/browse/MESOS-554
>             Project: Mesos
>          Issue Type: Improvement
>          Components: jenkins
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>             Fix For: 0.14.0
>
>
> Ideally should relaunch a jenkins slave when the corresponding Mesos task goes LOST.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira