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: [email protected] [mailto:[email protected]] On Behalf Of Jeff Schroeder Sent: mercredi 24 juin 2015 14:54 To: [email protected] 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 <[email protected]<mailto:[email protected]>> 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
