How the Jenkins project had to grow infrastructure overnight, and how a costly mistake doing things the wrong way forced us to migrate to managing our infrastructure with Puppet.
In early 2011 the Jenkins project became the Jenkins project, leaving
behind an organically grown but Oracle (formerly Sun) operated infrastructure.
An open source project with thousands of users had to grow an infrastructure
practically overnight, initially doing things "the wrong way" by hand crafting
machines. That was until a costly mistake forced us to reconsider and migrate
to managing our infrastructure with Puppet from a publicly available shared Git
repository.
Besides Puppet, the Jenkins project also uses a number of other tools to help
manage access control on GitHub, parts of JIRA, etc, all carrying on the very
transparent and welcoming tradition the project prides itself on.
In this talk I will discuss the ups and downs of switching an established
infrastructure to Puppet, all within the public eye and with volunteer time and
energy.