CI build can generate a versioned MSI file and push that out to Puppet. I
am creating an MSI with the same name, but different versions for each
release. Puppet detects the missing Package and properly installs the new
Package from MSI. However, Puppet does not detect that a new MSI needs to
replace the already installed package. My problem seems to be the same as this
closed issue <http://projects.puppetlabs.com/issues/13104>. I am running
3.1.0.
My plan for deployment has been to have each CI build create the
appropriately versioned MSI files and deploy them to Puppet as desired.
Then, let Puppet compare the MSI versions to the versions already
installed and install the new MSI if necessary.
Do I have a simple bug in my implementation or do I have a bad strategy. I
am considering the following:
1) Modify puppet windows package source to compare versions installed to
the version of the MSI.
2) Abort the MSI strategy and have each build generate a manifest that uses
the windows resources directly to complete the install (file, service,
scheduled task, IIS, etc). I think I will need to create an Assembly
resource that can install dlls to the GAC.
3) Put the version number as part of the package name. Thus forcing Puppet
to manage each version as a separate package. I'd rather not do this
because it will mean generating quite a bit of manifest code as part of the
build to ensure that previous versions are uninstalled and adding the new
version to the manifest.
Thanks,
Nathan
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
