From: Aleksander Morgado <aleksander@aleksander.es>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-12-09
Date: Wed, 11 Dec 2019 16:06:44 +0100 [thread overview]
Message-ID: <CAAP7ucL0VeyNS-e7xfxr5d2+e3ZZL9ad5t+Kdn=rC5AfB6gE_Q@mail.gmail.com> (raw)
In-Reply-To: <20191210212632.5bd43e99@windsurf>
Hey!
>
> > Is there any way I can reproduce that build locally? Not sure how to
> > exactly reproduce the build with the same toolchain and build options.
>
> To reproduce builds:
>
> (1) Download the br-reproduce-build script at
> http://git.buildroot.net/buildroot-test/plain/utils/br-reproduce-build
>
> (2) Run ./br-reproduce-build <hash of the build>
>
> The <hash of the build> is for example
> 0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a in
> http://autobuild.buildroot.net/results/0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a
>
> Otherwise, you can do that manually. In every build result directory,
> such as
> http://autobuild.buildroot.net/results/0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a,
> you have a file called "gitid" that contains the Buildroot commit at
> which the build was done, and a file called "config" that contains the
> Buildroot configuration.
>
> So essentially, what the br-reproduce-build script does is:
>
> $ git checkout $(curl http://autobuild.buildroot.net/results/0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a/gitid)
> $ make clean
> $ curl http://autobuild.buildroot.net/results/0ae6ca0b278ca1903057ff6ac31b1b70e8638b9a/config > .config
> $ make
>
That was extremely straightforward! Thanks for the tip.
--
Aleksander
https://aleksander.es
prev parent reply other threads:[~2019-12-11 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 7:18 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-12-09 Thomas Petazzoni
2019-12-10 18:20 ` Carlos Santos
2019-12-10 19:47 ` Aleksander Morgado
2019-12-10 20:26 ` Thomas Petazzoni
2019-12-11 15:06 ` Aleksander Morgado [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='CAAP7ucL0VeyNS-e7xfxr5d2+e3ZZL9ad5t+Kdn=rC5AfB6gE_Q@mail.gmail.com' \
--to=aleksander@aleksander.es \
--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.