From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] EXTRA_DOWNLOADS broken when SITE_METHOD = git
Date: Wed, 25 Apr 2018 23:06:43 +0200 [thread overview]
Message-ID: <20180425230643.39b21596@windsurf> (raw)
In-Reply-To: <5ae0ec96133d8_66723ff59b414878241cd@ultri4.mail>
Hello,
On Wed, 25 Apr 2018 18:01:10 -0300, Ricardo Martincoski wrote:
> I am currently refreshing my series with test cases for the git download infra.
Excellent! We will have to extend it to cover other download methods.
For example, the CVS backend got broken as a result of the recent
download infra changes.
> I think I can reuse the fixtures added by the series (static repo, br2-external)
> in order to add a test case for EXTRA_DOWNLOADS with SITE_METHOD = git.
>
> A simple solution probably will add one or few files to
> http://autobuild.buildroot.net/artefacts/
> to be used by the test case.
That can easily be done. I have no idea how scalable and future proof
this "artefacts" location is going to be, but we can start by using
that, and move to a better solution in the future if needed.
> Another way is to add a http server to the docker image to serve files added to
> support/testing to be used by the test case.
This also works. Seems a bit more complicated, no ?
> Yet another solution would be to build and run an image with a http server. The
> files to be served would be added to support/testing and copied to the image.
I did not understand this solution.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-25 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 8:56 [Buildroot] EXTRA_DOWNLOADS broken when SITE_METHOD = git Luca Ceresoli
2018-04-25 17:22 ` Yann E. MORIN
2018-04-25 17:46 ` Yann E. MORIN
2018-04-25 19:27 ` Thomas Petazzoni
2018-04-25 21:01 ` Ricardo Martincoski
2018-04-25 21:06 ` Thomas Petazzoni [this message]
2018-04-25 22:12 ` Ricardo Martincoski
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=20180425230643.39b21596@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.