Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Puppet manifests for managing the Jenkins project infrastructure
Puppet Shell ApacheConf Perl HTML Ruby
branch: master

Merge pull request #72 from jenkinsci/post-jira-migration

[INFRA-279] post-JIRA migration, disable JIRA on eggplant
latest commit 1b71c7f856
@kohsuke kohsuke authored
Failed to load latest commit information.
confluence.deb Added a packaging for 3.x
features Whitelist the nagios server for denyhosts to prevent it from stupidly…
local-modules [INFRA-279] post-JIRA migration, disable JIRA on eggplant
manifests Confluence post switch-over to lettuce.
.blimpignore Whitelist the nagios server for denyhosts to prevent it from stupidly…
.gitignore Add a basic Puppetfile containing the modules that were previously in…
.gitmodules Add the puppetlabs-apt module
Blimpfile Add HERO MODE to the Blimpfile for spinning up a number of machines t…
Gemfile Remove Vagrant from the Gemfile, it's now distributed via system pack…
Puppetfile Change the dependency on the puppet module to hit Puppet Forge
README.markdown Flesh out a basic readme
Rakefile Correct the Rakefile's lint target for the new local-modules tree
Vagrantfile need to load local modules as well.
cucumber.yml Add a good wip profile and default options for cucumber don't let local modifications from blocking puppet apply.


Jenkins CI Puppet Repository


In order to more effectively manage the Jenkins project's infrastructure these manifests have been created. There a couple of reasons for this:

  • Reproducibility: In the unfortunate scenario where a meteor falls on a datacenter where Jenkins hardware exists, we want to be able to bring a new host on to fulfill those needs as soon as possible.
  • Distributable: With Puppet manifests stored in this repository, it is easier to accept infrastructure help from members of the Jenkins community, without necessarily giving root access out.
  • Accountability: By funneling as much infrastructure work through Puppet as possible, we can have ensure the project has a very clear audit trail for specific infrastructure changes.

Getting Started

We use Vagrant to develop and test these manifests and as such there is a Vagrantfile already in the root directory. If you don't already have Vagrant:

% sudo gem install vagrant

Once you have vagrant you should be able to execute the following command to bring up a test virtual machine and provision it:

% vagrant up

For development, you can just create your manifests and include them in manifests/vagrant.pp, once you're ready to re-run the puppet manifests you can run the following command (no need to rebuild the VM):

% vagrant provision

Getting Help

If you have any questions, stop by the #jenkins channel on the Freenode network and ask rtyler.

Failing that, the jenkinsci-users@ mailing list is a good place to ask for help.

Something went wrong with that request. Please try again.