From: Frank Hoeflich <frankhoeflich@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildbot infrastructure
Date: Sat, 28 Feb 2009 16:04:39 -0800 (PST) [thread overview]
Message-ID: <608983.59657.qm@web56904.mail.re3.yahoo.com> (raw)
In-Reply-To: <8763ivkkit.fsf@macbook.be.48ers.dk>
Peter:
Actually I was hunting for any BR support for the next step - kicking off an automated test cycle after a config builds correctly. If that doesn't exist yet (and no one else has claimed this turf), I'll go off into a corner and figure out how to write something for buildbot.
Thank you for putting me into the ballpark.
--Frank
--- On Sat, 2/28/09, Peter Korsgaard <jacmet@uclibc.org> wrote:
> From: Peter Korsgaard <jacmet@uclibc.org>
> Subject: Re: buildbot infrastructure
> To: frankhoeflich at yahoo.com
> Cc: jacmet at uclibc.org, buildroot at busybox.net
> Date: Saturday, February 28, 2009, 12:55 AM
> >>>>> "Frank" == Frank Hoeflich
> <frankhoeflich@yahoo.com> writes:
>
> Hi,
>
> Frank> I tried to look into this and couldn't find
> anything for
> Frank> buildbot in my copy of the tree. Is it
> available for
> Frank> developers to inspect?
>
> We don't have anything in the tree, but setting up
> buildbot is quite
> easy. I have it running at work for the targets we're
> using.
>
> Building is just a matter of:
>
> svn update
> yes ''|make <target>_defconfig
> yes ''|make
>
> Or in buildbot syntax:
>
> f1 = factory.BuildFactory()
> f1.addStep(SVN(svnurl=SVNURL, mode="copy"))
> f1.addStep(Configure(command="yes ''|make
> "+target + "_defconfig"))
> f1.addStep(Compile(command="yes ''|make
> -s"))
>
> The yes '' stuff is for when buildroot asks for
> user input.
>
> --
> Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-03-01 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 23:44 [Buildroot] buildbot infrastructure Frank Hoeflich
2009-02-28 8:55 ` Peter Korsgaard
2009-03-01 0:04 ` Frank Hoeflich [this message]
2009-03-01 6:43 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=608983.59657.qm@web56904.mail.re3.yahoo.com \
--to=frankhoeflich@yahoo.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox