[Buildroot] [RFC] Continuous integration

Matthew Weber mlweber1 at rockwellcollins.com
Mon Nov 11 13:53:45 UTC 2013

Maxime Ripard <maxime.ripard at free-electrons.com> wrote on 11/10/2013 
05:18:11 AM:

> From: Maxime Ripard <maxime.ripard at free-electrons.com>
> To: Matthew Weber <mlweber1 at rockwellcollins.com>
> Cc: Jérôme Pouiller <jezz at sysmic.org>, buildroot at busybox.net
> Date: 11/10/2013 05:20 AM
> Subject: Re: [Buildroot] [RFC] Continuous integration
> Hi Matthew,
> On Fri, Nov 08, 2013 at 01:35:46PM -0600, Matthew Weber wrote:
> > We might have a fourth semi-continuous integration scenario that 
> > server thrashing at each check-in. 
> > - We run the script every night processing the current GIT tip at that 

> > time. 
> > - We clean each of the full cfg builds and let the script do a 
> > re-build.  (We do this because the individual pkg  cleans aren't 
> > guaranteed 
> > to cleanup the pkg installs)
> > - Once all jobs complete we terminate the script and eventually will 
> > the report with status.
> > (I'll clean-up what I changed and get it committed.  Would you be up 
> > optional runtime config options?  One might be to enable continuous 
> > or a one-stop script execution.)
> It's pretty much what I've setup here already:
> http://jenkins.free-electrons.com/job/buildroot/
> It runs every night and start a clean build of all the configuration
> we have if a new commit has been merged.
> The only thing missing here is that the emails get only send to Peter,
> Thomas P. and I because I didn't want to spam the list, but this can
> easily be changed.
Cool, good to know that the default set of defconfigs is being validated 
the current tip.
I think the scenario we're trying to target is validating offline/internal 

board targets for different custom products.  We don't necessarily want 
the builds
to catch every commit (limited on build server resources), but just give 
us granular
enough feedback to know roughly which commit caused a new issue. 
We evaluated buildbot and Jenkins and had been debating about just doing a 

simple script like what Jérôme has done.  So when we saw what he had 
started it 
looked like a good opportunity to give it a try.  Currently we have it 
setup for
a nightly validation of a few defconfigs. 
For a continuous integration, I do agree Jenkins is a very good option.

Matt Weber
mlweber1 at rockwellcollins.com

> Maxime
> -- 
> Maxime Ripard, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> [attachment "signature.asc" deleted by Matthew L Weber/CedarRapids/
> RockwellCollins] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131111/89080467/attachment-0002.html>

More information about the buildroot mailing list