Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Server automation framework and application
Ruby HTML Shell Puppet Emacs Lisp Makefile Other
branch: master
Failed to load latest commit information.
acceptance Merge remote-tracking branch 'upstream/stable'
api (PUP-3809) Move code directories to /etc/puppetlabs/code
autotest (maint) Ensure every file has a trailing newlines
benchmarks (maint) Adds environment functions to function loading performance test
bin (PUP-2563) Exit with 1 on pre-1.9.3 ruby
conf (PUP-4094) Update environment_timeout default in example environment.…
docs Merge pull request #3709 from kylog/docs/spec-order
examples/hiera (Maint) Update commands to use new forms in hiera examples
ext Merge pull request #3822 from whopper/PUP-4388/master/debian-remove-d…
lib Merge branch 'stable'
man (maint) Update manpages to remove master_url_prefix setting
spec Merge pull request #3684 from onyxpoint/PUP-1253
tasks (PUP-3912) Add legacy_formatters gem for junit integration
util (PUP-3912) Update parallel:spec task for rspec 3
yardoc/templates/default (#18023) Document user facing classes using yardoc and show api.
.gemspec (PUP-3920) Make puppet depend on hiera 2.0
.gitignore (maint) Update CI Setup for AIO Testing
.mailmap (maint) Update mailmap for git shortlog
.noexec.yaml (#15464) Exclude gem command from bundler
.rubocop.yml (maint) Enable rubocop checking for shadowed variables
.travis.yml Revert "(maint) Remove travis sudo: false setting"
.yardopts (maint) Remove reference to README_DEVELOPER (maint) Clarify the merge-up process in COMMITTERS Merge branch 'stable'
Gemfile (PUP-3290) Update hiera version to 2.0 under ext
LICENSE (maint) Update copyright years in LICENSE (maint) Update docs badge in README
Rakefile (PUP-2563) Remove rubocop task's check for ruby 1.8.7
appveyor.yml (PUP-585) Add AppVeyor CI configuration
install.rb Merge pull request #3742 from joshcooper/ticket/master/PUP-4194-reloc…


Build Status Inline docs

Puppet, an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.


Documentation for Puppet and related projects can be found online at the Puppet Docs site.




The best way to run Puppet is with Puppet Enterprise, which also includes orchestration features, a web console, and professional support. The PE documentation is available here.

To install an open source release of Puppet, see the installation guide on the docs site.

If you need to run Puppet from source as a tester or developer, see the running from source guide on the docs site.

Developing and Contributing

We'd love to get contributions from you! For a quick guide to getting your system setup for developing take a look at our Quickstart Guide. Once you are up and running, take a look at the Contribution Documents to see how to get your changes merged in.

For more complete docs on developing with puppet you can take a look at the rest of the developer documents.


See LICENSE file.


Please log tickets and issues at our JIRA tracker. A mailing list is available for asking questions and getting help from others. In addition there is an active #puppet channel on Freenode.

We use semantic version numbers for our releases, and recommend that users stay as up-to-date as possible by upgrading to patch releases and minor releases as they become available.

Bugfixes and ongoing development will occur in minor releases for the current major version. Security fixes will be backported to a previous major version on a best-effort basis, until the previous major version is no longer maintained.

For example: If a security vulnerability is discovered in Puppet 4.1.1, we would fix it in the 4 series, most likely as 4.1.2. Maintainers would then make a best effort to backport that fix onto the latest Puppet 3 release.

Long-term support, including security patches and bug fixes, is available for commercial customers. Please see the following page for more details:

Puppet Enterprise Support Lifecycle

Something went wrong with that request. Please try again.