Submitted by kohsuke on Thu, 2014-05-08 08:58
As the Jenkins project grows, the need for our infrastructure has been growing. Our Jenkins-on-Jenkins needs more build slaves, we need more servers to run our infrastructure services.
And it was once again Rackspace who stepped up to the plate; they have kindly donated us more cloud servers. I also use Rackspace for one of my personal servers, and when I went back to their admin console this time, I noticed that they've added a lot more services to their offering.
I am setting up these boxes as I write this. A huge thank you for Rackspace for their support of this project. And if you are interested in using Rackspace cloud servers as elastic build slaves, jclouds plugin is your friend.
Agenda is posted for Jenkins User Conference Boston and Berlin.
For Boston, my favorite would be the workflow in Jenkins talk that will cover the new workflow job type Jesse and I are working on. As of this writing it is still very much a work in progress, but that talk is our way of putting a stake on the ground that we WILL have something we can talk about by then. There's also some talks that describes how they've put together pieces (including Jenkins) to create a broad automation, such as Distributed Scrum Development with Jenkins, Vagrant, Fabric and Selenium and Moving Existing Enterprise Systems to Continuous Integration and Deployment with Jenkins.
We are looking for volunteers to join the small infra team here at the Jenkins project. We are the butlers of the butler that get Mr.Jenkins going.
We've been managing our servers through puppet, and have been slowly folding pieces one at a time to puppet, but there's still a lot of snowflake services that need proper operationalization.
So to fix them up, PuppetLabs folks generously agreed to help us get going with a deployment of Puppet Enterprise. Tyler has managed to arrange a "rapid deployment" engagement. To kick start the effort, an instructor would come for one week (April 28th-May 2nd) to bring us up to speed on modern Puppet. we'll then spend some time on our own to puppt-ize more, and deploy Puppet Enterprise.
The end goal is to ensure sustainability of our infrastructure, in case of unexpected server loss.
One of the new efforts in Jenkins this year is the acceptance test harness for Jenkins.
We will be doing the Jenkins office hours next week to go over this and sync up and coordinate between people in the community that are trying to work on this.
It'll be April 23rd 11am PT (see what this time is in your time zone) on Google Hangout at http://jenkins-ci.org/hangout. If you are intereste in hacking Jenkins or if you are a large user of Jenkins who have acceptance tests, we are looking forward to seeing you there.
For those of you who haven't looked, this test harness allows you to write blackbox tests of Jenkins and its plugins. It was originally used to test LTS releases, but over the time, it acquired a number of features, such as ...:
- Docker support for launching complex fixtures to test Jenkins with.
- Pluggability to launch Jenkins under test (JUT) in many different environments