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

Posted to user@mesos.apache.org by Vladimir Vivien <vl...@gmail.com> on 2013/09/29 13:02:48 UTC

Question about Mesos Jenkins Plugin Code

Vinod,
Looking at the Mesos Jenkins code, I noticed there's no explicit Executor.
 What mechanism is sending update to the scheduler to mark a task FINISHED,
for instance?

-- 
Vladimir Vivien

Re: Question about Mesos Jenkins Plugin Code

Posted by Vladimir Vivien <vl...@gmail.com>.

Vinod,
I kinda figure that was the behavior.  Thanks for confirming.


On Sun, Sep 29, 2013 at 6:51 PM, Vinod Kone <vi...@gmail.com> wrote:

> Hey Vladimir,
>
> The Jenkins scheduler utilizes the default executor (called Command
> executor) provided by Mesos. The Command executor simply runs a command and
> exits when the command finishes. See src/launcher/executor.cpp for more
> details.
>
> HTH,
>
>
> On Sun, Sep 29, 2013 at 4:02 AM, Vladimir Vivien <
> vladimir.vivien@gmail.com> wrote:
>
>> Vinod,
>> Looking at the Mesos Jenkins code, I noticed there's no explicit
>> Executor.  What mechanism is sending update to the scheduler to mark a task
>> FINISHED, for instance?
>>
>> --
>> Vladimir Vivien
>>
>
>


-- 
Vladimir Vivien

Re: Question about Mesos Jenkins Plugin Code

Posted by Vinod Kone <vi...@gmail.com>.

Hey Vladimir,

The Jenkins scheduler utilizes the default executor (called Command
executor) provided by Mesos. The Command executor simply runs a command and
exits when the command finishes. See src/launcher/executor.cpp for more
details.

HTH,

On Sun, Sep 29, 2013 at 4:02 AM, Vladimir Vivien
<vl...@gmail.com>wrote:

> Vinod,
> Looking at the Mesos Jenkins code, I noticed there's no explicit Executor.
>  What mechanism is sending update to the scheduler to mark a task FINISHED,
> for instance?
>
> --
> Vladimir Vivien
>