Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [ANNOUNCE] Autobuilder script available, join the autobuilder effort!
Date: Tue, 17 Jun 2014 13:00:25 +0200	[thread overview]
Message-ID: <20140617130025.664a1df6@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LWy4ysqMhrQ=FMZszUoyYzd_711VfCCgSUTO_WwTQ8vbA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Tue, 17 Jun 2014 12:24:53 +0200, Thomas De Schampheleire wrote:

> First of all thanks a lot for making this available!

And thanks a lot to you for being apparently the first person to test
the script. Again, please be tolerant with my horrible Python skills
exposed throughout the script :)

> I am currently testing the script, and hope to get permission to run
> it during the night on one or more work machines.
> I had to make one modification currently: since we are behind a
> firewall, running 'git' directly is not possible, but I need to use a
> wrapper script. I added this:
> 
> +try:
> +    gitcmd = os.environ['GIT']
> +except KeyError:
> +    gitcmd = 'git'
> 
> at the top of the script, and replaced all direct occurrences of 'git'
> with gitcmd.
> This allows me to run 'GIT=git-wrapper autobuild-run'.
> 
> I used an environment variable because it seemed superfluous to add a
> configuration variable for it, but if you prefer I can do that too.

I don't have a very strong preference here. Perhaps having it defined
in the configuration file would be better, as it is more similar to
what we do for the other configuration parameters?

Do not hesitate to send me patches, the Git repository is at
git://git.busybox.net/buildroot-test.

> Is there an easy way to get a web interface like that on
> autobuild.buildroot.org, for the locally created builds? This would
> make it easy to inspect the results while testing (for example to see
> that some host package like 'bzr' needed to be installed, ...).

Well, the autobuild.buildroot.org interface is itself available in
git://git.busybox.net/buildroot-test. However, setting it up will
require a bit of configuration (PHP, MySQL + one database). You could
then submit your builds to your own autobuilder instance for testing,
and then decide to switch to the main autobuilder instance at
autobuild.buildroot.org once you believe things are stable enough.

Thanks again for your feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-06-17 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 19:23 [Buildroot] [ANNOUNCE] Autobuilder script available, join the autobuilder effort! Thomas Petazzoni
2014-06-17 10:24 ` Thomas De Schampheleire
2014-06-17 11:00   ` Thomas Petazzoni [this message]
2014-06-18  7:31     ` Thomas De Schampheleire
2014-06-18  8:25       ` Thomas Petazzoni
2014-06-18  8:47         ` Thomas De Schampheleire
2014-06-18  8:51           ` Thomas Petazzoni
2014-06-18  9:23             ` Thomas De Schampheleire
2014-06-18 11:51         ` Thomas De Schampheleire
2014-06-19 12:40           ` Thomas Petazzoni
2014-06-20 21:03 ` Matthew Weber
2014-06-21 17:20   ` Thomas Petazzoni
2014-06-22 18:37     ` Matthew Weber

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=20140617130025.664a1df6@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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