On Tue, Mar 5, 2013 at 6:31 PM, Nathan Shirlberg wrote:
> Thanks for the suggestion. I'll look into that. I have started appending
> the version to the package name and with the plan to use something like
> hiera as a lookup to determine what version should be on each machine. We
> would have the
Thanks for the suggestion. I'll look into that. I have started appending the
version to the package name and with the plan to use something like hiera as a
lookup to determine what version should be on each machine. We would have the
build server publish each version to puppet as an artifact and
Hi Nathan,
On Mar 4, 2013, at 8:57 AM, Nathan Shirlberg wrote:
> I want to use Puppet to manage deployment of internal .Net software. The 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 rel
I want to use Puppet to manage deployment of internal .Net software. The
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