[systemd-devel] Broken build and CI strategy

Holger Hans Peter Freyther holger at freyther.de
Thu Jun 27 23:50:47 PDT 2013


Dear Lennart,

the systemd build is currently broken[1] and judging from the commit
history it appears that this happened more than once. Besides fixing
the build you might want to consider adopting another strategy.

In mature software projects the following is quite common:

a.) Create a .travis.yml, sync your repo to github[2] and have
travis-ci build your code. My .travis.yml file for systemd is
here[3]. Travis can send email to the repo owners/travis owners
on failed builds.

b.) Use a combination of gerrit/jenkins. E.g. if you don't want
to have broken builds in master. One would push changes for review to
Gerrit, these would be automatically build on a Jenkins system
and if they compile they can be integrated into the main repository.
The workflow is used in projects like coreboot.


cheers
	holger


[1] https://travis-ci.org/zecke/systemde/builds/8530934
[2] github can create official mirrors of repositories but they only
sync a couple of times/once a day.
[3] https://github.com/zecke/systemde/blob/master/.travis.yml


More information about the systemd-devel mailing list