You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Sebastien Brennion <se...@leanbi.ch> on 2015/06/24 14:50:13 UTC
git / chronos-marathon integration
Is there a way to specify which version of a script marathon/chronos should use ? :
I would like being able to have multiple version of a job, and being able to set a specific version productive, so that at this moment, mesos is getting and using that version (for marathon and chronos)...
Do somebody already have something similar ?
Regards,
Sébastien
Re: git / chronos-marathon integration
Posted by zhou weitao <zh...@gmail.com>.
And our team is do version control by the docker tag as you said. But you'd
better to keep an eye on the disk resource taken by the increasing docker
images.
2015-06-24 21:04 GMT+08:00 haosdent <ha...@gmail.com>:
> docker have tag for images. I think you could use it to do version control
> on container.
>
> On Wed, Jun 24, 2015 at 9:00 PM, Sebastien Brennion <
> sebastien.brennion@leanbi.ch> wrote:
>
>> In fact that would be the result of it…
>>
>> But I would like to find a way doing something like :
>>
>> - indicate mesos “version 1.3 is productive”
>>
>> - mesos checking which version it has, eventually performing a git clone
>> or similar
>>
>> - if needed restarting marathon jobs
>>
>> - running further chronos jobs with the right version…
>>
>>
>>
>> The Idea would be to automatize this somehow..
>>
>>
>>
>> *From:* jeffschroed@gmail.com [mailto:jeffschroed@gmail.com] *On Behalf
>> Of *Jeff Schroeder
>> *Sent:* mercredi 24 juin 2015 14:54
>> *To:* user@mesos.apache.org
>> *Subject:* Re: git / chronos-marathon integration
>>
>>
>>
>> And I guess git clone with -b for a branch name or specifying a commit
>> manually won't work for you?
>>
>> On Wednesday, June 24, 2015, Sebastien Brennion <
>> sebastien.brennion@leanbi.ch> wrote:
>>
>> Is there a way to specify which version of a script marathon/chronos
>> should use ? :
>>
>>
>>
>> I would like being able to have multiple version of a job, and being able
>> to set a specific version productive, so that at this moment, mesos is
>> getting and using that version (for marathon and chronos)…
>>
>>
>>
>> Do somebody already have something similar ?
>>
>> Regards,
>>
>> Sébastien
>>
>>
>>
>> --
>> Text by Jeff, typos by iPhone
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: git / chronos-marathon integration
Posted by haosdent <ha...@gmail.com>.
docker have tag for images. I think you could use it to do version control
on container.
On Wed, Jun 24, 2015 at 9:00 PM, Sebastien Brennion <
sebastien.brennion@leanbi.ch> wrote:
> In fact that would be the result of it…
>
> But I would like to find a way doing something like :
>
> - indicate mesos “version 1.3 is productive”
>
> - mesos checking which version it has, eventually performing a git clone
> or similar
>
> - if needed restarting marathon jobs
>
> - running further chronos jobs with the right version…
>
>
>
> The Idea would be to automatize this somehow..
>
>
>
> *From:* jeffschroed@gmail.com [mailto:jeffschroed@gmail.com] *On Behalf
> Of *Jeff Schroeder
> *Sent:* mercredi 24 juin 2015 14:54
> *To:* user@mesos.apache.org
> *Subject:* Re: git / chronos-marathon integration
>
>
>
> And I guess git clone with -b for a branch name or specifying a commit
> manually won't work for you?
>
> On Wednesday, June 24, 2015, Sebastien Brennion <
> sebastien.brennion@leanbi.ch> wrote:
>
> Is there a way to specify which version of a script marathon/chronos
> should use ? :
>
>
>
> I would like being able to have multiple version of a job, and being able
> to set a specific version productive, so that at this moment, mesos is
> getting and using that version (for marathon and chronos)…
>
>
>
> Do somebody already have something similar ?
>
> Regards,
>
> Sébastien
>
>
>
> --
> Text by Jeff, typos by iPhone
>
--
Best Regards,
Haosdent Huang
RE: git / chronos-marathon integration
Posted by Sebastien Brennion <se...@leanbi.ch>.
In fact that would be the result of it…
But I would like to find a way doing something like :
- indicate mesos “version 1.3 is productive”
- mesos checking which version it has, eventually performing a git clone or similar
- if needed restarting marathon jobs
- running further chronos jobs with the right version…
The Idea would be to automatize this somehow..
From: jeffschroed@gmail.com [mailto:jeffschroed@gmail.com] On Behalf Of Jeff Schroeder
Sent: mercredi 24 juin 2015 14:54
To: user@mesos.apache.org
Subject: Re: git / chronos-marathon integration
And I guess git clone with -b for a branch name or specifying a commit manually won't work for you?
On Wednesday, June 24, 2015, Sebastien Brennion <se...@leanbi.ch>> wrote:
Is there a way to specify which version of a script marathon/chronos should use ? :
I would like being able to have multiple version of a job, and being able to set a specific version productive, so that at this moment, mesos is getting and using that version (for marathon and chronos)…
Do somebody already have something similar ?
Regards,
Sébastien
--
Text by Jeff, typos by iPhone
Re: git / chronos-marathon integration
Posted by Jeff Schroeder <je...@computer.org>.
And I guess git clone with -b for a branch name or specifying a commit
manually won't work for you?
On Wednesday, June 24, 2015, Sebastien Brennion <
sebastien.brennion@leanbi.ch> wrote:
> Is there a way to specify which version of a script marathon/chronos
> should use ? :
>
>
>
> I would like being able to have multiple version of a job, and being able
> to set a specific version productive, so that at this moment, mesos is
> getting and using that version (for marathon and chronos)…
>
>
>
> Do somebody already have something similar ?
>
> Regards,
>
> Sébastien
>
--
Text by Jeff, typos by iPhone