[systemd-devel] Broken build and CI strategy

[Peter Sztanojev]

On Fri, Jun 28, 2013 at 8:50 AM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> 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.
>

there already is a jenkins ci for systemd kindly provided by Pantheon:
http://systemd.getpantheon.com:8080/jenkins/
The output of which can be seen on IRC.
The problems always seem to come from non-standard/broken setups

>
> 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
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel