In the past, I''ve used Jenkins to automate package builds. It can be
set up
to trigger a new build after git updates, then just have puppet ensure
latest on that package.
Setting up new packages wasn''t usually that bad, as the script
wasn''t that
different between the apps. I''ll admit spec files are still not fun to
deal
with.
On Monday, July 1, 2013 10:22:17 AM UTC-7, Rance Hall
wrote:>
> We have an issue with a puppet manifest that installs a web app
>
> The install works fine, but we need a way to upgrade the app when new
> versions are released.
>
> We manage a git repo with the source code for the web app.
>
> The puppet manifest downloads from the git repo and all is well.
>
> We need a way to trigger a fresh download from the git repo and run some
> of the automatic database migration scripts when we deploy a new version.
>
> I started with a version tracking file and hopefully changing the file
> would trigger something, but it does not work the way we want.
>
> I can fire of an exec script from the notify option when the file changes,
> but this is ineffective because I would need to rescript all the
> differences between sites which are already part of our puppet structure.
>
> converting the web app to a package is not an option due to the number of
> packages we would be forced to maintain.
>
> Ideas?
>
>
>
--
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+unsubscribe@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.
For more options, visit https://groups.google.com/groups/opt_out.