On Sun, May 5, 2013 at 2:11 PM, Larry Fast <lfast1...@gmail.com> wrote:
> What about the larger processes involved in incremental updates? Eg.
> sequencing your updates so that the service keeps running. I'm considering
> using Jenkins to orchestrate sequencial activity.
Coming from an ISConf background, I'd do it makefile-style.
Have actions that indicate completion by touching an empty file, and
tell puppet about it with a "creates".
exec { "/usr/local/puppetactions/frambulant-upgrade-v1-v2":
...
creates => '/var/lib/puppetactions/frambulant-upgrade-v1-v2'}
}
exec { "/usr/local/puppetactions/frambulant-upgrade-v2-v3":
...
requires => Exec['/usr/local/puppetactions/frambulant-upgrade-v1-v2']
creates => '/var/lib/puppetactions/frambulant-upgrade-v2-v3'}
}
Haven't actually used this yet, but my reading of
https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/ssn6t2B8us0
is that it would work...
TBH, I am not familiar with Jenkins, perhaps it does something else?
m
--
martin.langh...@gmail.com
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
