From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] gitlab-ci: add .config to artefacts
Date: Sat, 30 Dec 2017 22:36:13 +0100 [thread overview]
Message-ID: <20171230223613.09531f66@windsurf> (raw)
In-Reply-To: <20171220141933.27736-1-yann.morin.1998@free.fr>
Hello,
On Wed, 20 Dec 2017 15:19:33 +0100, Yann E. MORIN wrote:
> The defconfig is dumped at the very beginning of the build log, but the
> resulting .config is still interesting to get, in case some settings did
> not end up in there (e.g. because of the host gcc version, or because of
> conflicting settings, or because the Config.in changed without the tests
> being updated, or...).
>
> So, add the .config to the list of artefacts to save.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
>
> ---
> Changes v1 -> v2:
> - update .gitlab-ci.yml.in too (Ricardo)
> - update commit log to refer to the defconfig (Ricardo)
> - (s/artifact/artefact/, to use the english spelling, not the
> american one (Ricardo ;-] )
> ---
> .gitlab-ci.yml | 1 +
> .gitlab-ci.yml.in | 1 +
> 2 files changed, 2 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-30 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 14:19 [Buildroot] [PATCHv2] gitlab-ci: add .config to artefacts Yann E. MORIN
2017-12-21 2:26 ` Ricardo Martincoski
2017-12-30 21:36 ` 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=20171230223613.09531f66@windsurf \
--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