veyepar: Scaling OpenStack Development with git, Gerrit and Jenkins

Author(s):	Monty Taylor,James Blair
Location	T101
Date	jan Tue 17	Days Raw Files
Start	14:20	First Raw Start	error-in-template
Duration	0:50:00	Offset	None
End	15:10	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2012.linux.org.au/schedule/182/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Scaling_OpenStack_Development_with_git_Gerrit_and_Jenkins.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

The OpenStack Project has seen a phenomenal growth in its first year and a half. Part of the reason that we've been able to handle the dramatic influx in developers is by having automation systems that allow us to treat all developers equally from a process perspective, keep our trunk always clean by performing testing pre-merge and still be streamlined enough that the process did not get in the way of development.

James Blair and I will start with a brief (very brief) history of where we started and the techniques we employed at first, including bzr, launchpad and tarmac. We had some wins and learned some excellent lessons from the early setup.

We'll move quickly on to the meat though, which is the design and implementation of the current system, based around a combination of gerrit and jenkins. We'll cover the workflow that we support and require, how we implemented it and what the challenges were.

At the end of the talk, you should come away with a good sense of why we made the choices we made and how they might be applicable to your project, and how to go about implementing them. You should also have been convinced that any process which does not employ pre-merge testing is doomed to failure. :)

Comment:

production notes