From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] autobuilder sandbox
Date: Mon, 22 Oct 2018 15:16:41 +0200 [thread overview]
Message-ID: <20181022151641.198b2c3f@windsurf> (raw)
In-Reply-To: <CANQCQpa_R+UwyhmNZGeKyOtN2G3487r6-T8zaDayGufq7g2g3g@mail.gmail.com>
Hello,
On Mon, 22 Oct 2018 04:23:08 -0500, Matthew Weber wrote:
> I was able to get a script using the bubblewrap project working. It
> remaps the mounted filesystem environment read-only around the
> application/shell you call. I was wondering what the best strategy
> would be to start introducing these type of build failures?
The best strategy is to *not* introduce build failures :-)
> Maybe the autobuilder support for an alternate repo and branch needs
> to be merged first?
Well supporting alternate repo/branch is about testing different
Buildroot versions, not about testing in different environments.
I think we don't need anything special: an autobuild instance running
in a sandbox can be considered as just another autobuild instance. Just
like some autobuild instance run with Debian, others with Fedora, with
varying versions of distributions and installed packages.
So you could have an autobuilder instance running inside a sandboxed
environment, and report results to autobuild.buildroot.org with a
clearly identified "submitter" content that allows to know it's a
sandboxed instance.
To run this, I guess you have two options:
- Run the entire autobuild-run stuff in a sandbox.
- Modify autobuild-run so that it can optionally run just the build
inside a sandbox.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-22 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 9:23 [Buildroot] autobuilder sandbox Matthew Weber
2018-10-22 13:16 ` Thomas Petazzoni [this message]
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=20181022151641.198b2c3f@windsurf \
--to=thomas.petazzoni@bootlin.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