Author(s):	Michael Prokop
Location	Berlin/London
Date	aug Mon 17	Days Raw Files
Start	14:00	First Raw Start	error-in-template
Duration	00:45:00	Offset	None
End	14:45	Last Raw End
Chapters
Total cuts_time	None min.

https://summit.debconf.org/debconf15/meeting/286/continuous-delivery-of-debian-packages/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	How would it be to just commit your packaging changes to the version control system and get automated Q/A tests plus Debian packages for different releases without any further manual work required? This is what we're doing for a company who relies 100% on Debian packages. The OpenStack project jenkins-job-builder allows us to manage more than 800 Jenkins jobs through a few YAML configuration files without touching the Jenkins web interface. jenkins-debian-glue takes care of Debian package builds, building on cowbuilder, lintian, piuparts and autopkgtest. Code review using Gerrit as well as configuration management (Puppet + Ansible) helps us control the workflow and infrastructure. All the involved software is open source and in this talk I'll provide an overview how such a system can look like, how you might benefit for your own project and which challenges you might face. markdown
Comment:	production notes