At work, our old code deployment strategy was basically a wrapper script doing an svn checkout and some symlinking. With our move to Puppet for config management, we also moved to using Apt packaging for our code deployment, tying them together with a line similar to :
class foo-export {
package { 'foo-export': ensure => latest }
}
So that whenever we deploy a new version of a package to our apt-repo, it can then be installed with a:
puppet agent --test
(and with an initial dry-run using --noop)
( I should mention I manage our Puppet runs via our own distributed scripts, rather than having the nodes set up to check in every 30mins - when I'm doing so much work on our Puppet setup and config, I'd rather not having machines check in automatically in case the config is in a broken state )
Inevitably I would run the above Puppet command and it would not find any new packages, because ‘d'uh!', of course I still need to run an apt-get update.
I've been using Puppet stages for a while now, in order to group package installations in a broader sense rather than manually spelling out every dependency with a require => stanza, so it was a simple addition to add in a pre stage, and have the nodes run apt-get update before any runs.
In order to use stages, you need to first define them in your site.pp. By default every defined class runs under Stage[main], so you just need to add the new stages and define the running order. (full Puppet stage documentation is here)
At the top of my site.pp file, I added a pre and post stage, then define the execution order via:
stage { [pre, post]: }
Stage[pre] -> Stage[main] -> Stage[post]
Then I created a class called apt-hupdate (sorry, i use stupid naming conventions!) inmodules/apt-hupdate/manifests/init.pp
which contained:class apt-hupdate {
exec { "aptHupdate":
command => "/usr/bin/apt-get update",
}
}
And finally, include that in your site.pp with:
class { apt-hupdate: stage => pre }
Now every time you do a Puppet run, apt-get update will be the first task run.