From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] scripts/autobuild-run: add --branches option
Date: Wed, 16 Jan 2019 09:55:04 +0100 [thread overview]
Message-ID: <20190116095504.434690f6@windsurf> (raw)
In-Reply-To: <20190115141131.22754-1-arnout@mind.be>
Hello,
On Tue, 15 Jan 2019 15:11:31 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> From: Arnout Vandecappelle <arnout.vandecappelle@essensium.com>
>
> The autobuild-run script will retrieve the list of branches to test
> from autobuild.buildroot.org. However, it the autobuild script is used
> to test some local configuration, this is probably not appropriate. The
> new --branches option allows to override the URL of the branches CSV
> file. A file:/// URL can be used for a local file.
>
> Signed-off-by: Arnout Vandecappelle <arnout.vandecappelle@essensium.com>
I had an alternate patch ready for this, which consists in changing
http-url to be the base URL, and not the submission URL.
I.e:
'--http-url': 'http://autobuild.buildroot.org/submit/',
would become:
'--http-url': 'http://autobuild.buildroot.org/',
And so the branches file would be retrieved from $(--http-url)/branches.
Would this work for you, or do you have a set up where the branches
file is not located at the same place as the submission URL ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-16 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 14:11 [Buildroot] [PATCH] scripts/autobuild-run: add --branches option Arnout Vandecappelle
2019-01-16 8:55 ` Thomas Petazzoni [this message]
2019-01-16 11:58 ` Arnout Vandecappelle
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=20190116095504.434690f6@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.