Search code examples
chef-infrapuppetnexusartifactory

Where to store installation packages for Chef/Puppet?


This is the same question as this one, but I have no right to comment so have to start a new question: Where to Store Local Software Packages for Chef Recipe

We are using Jenkins to push the build result into Nexus/Artifactory, and using UrbanCode to do the deployment to the servers in the target environments. The infrastructure guys are using Chef to do their installation such as IIS. Now they are asking me, can they use Nexus/Artifactory to store their installation package.

My concern is these installation exe, msi, etc are very large. Would like to ask your experience.

Thanks Jirong


Solution

  • A proper artifact repository is a great choice for storing Ops-releated binaries, and those tools are specially designed for handling large files. For example, with Artifactory you get deduplication out of the box with checksum-based storage, optimized uploads with checksum-based uploads, ability to connect NAT as a binaries storage or even get an "infinite" storage on S3-compatible FS.

    Regarding the file types, although the repositories don't list special support for .exe and .msi files, it works great, cause those files doesn't require any special support. Once you can setup your files in Maven layout they will work in Nexus. Or you can have setup the files in any way you like and use Artifactory.


    I am with JFrog, the company behind Bintray and [artifactory], see my profile for details and links.