veyepar: How OpenStack Improves Code Quality with Project Gating and Zuul

Author(s):	James Blair
Location	MCC4
Date	feb Fri 01	Days Raw Files
Start	13:20	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	14:05	Last Raw End
Chapters
Total cuts_time	None min.

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

assets release.pdf How_OpenStack_Improves_Code_Quality_with_Project_Gating_and_Zuul.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 uses project gating to ensure that the latest
code in the repository always works.  Gating is a process where every
change, after passing code review, is automatically tested and merged
only if it passes the test suite.  Especially for large projects with
complex test suites, this process can keep code quality high while
making it easier to accept patches from new contributors.

The OpenStack CI team developed Zuul to manage its project gating
system.  Zuul is a flexible, general purpose system to integrate
Gerrit code review and Jenkins and can be used for project automation
purposes beyond trunk gating.  Driven by a simple, readable YAML file,
Zuul has a set of basic concepts that can be combined to make very
powerful automation pipelines.  Zuul can perform speculative execution
of tests on multiple dependent changes in parallel to keep merges
happening quickly for gated projects.

This presentation will review how OpenStack uses project gating as
well as the capabilities of Zuul and how to set up a similar system
for any project.

Comment:

production notes