Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gitlab-ci: add .config to artefacts
Date: Wed, 20 Dec 2017 14:15:23 +0100	[thread overview]
Message-ID: <20171220131523.GA21413@scaer> (raw)
In-Reply-To: <5a387281cf61_bd03fa772a46ee8855bb@ultri3.mail>

Ricardo, All,

On 2017-12-18 23:59 -0200, Ricardo Martincoski spake thusly:
> On Mon, Dec 18, 2017 at 07:25 PM, Yann E. MORIN wrote:
> > When a run-time test fails to build, it is interesting to get the
> > corresponding .config file directly as an artifact, rather than
> > reconstruct it manually from the various config snippets embedded
> > in the many runtime-test scripts.
> 
> The defconfig is already dumped to the beginning of the build log.

Ah, right, that would have been enough for my use-case.

> But I agree that having also the .config can be handy (we have both in the
> autobuilder results).

Yes, because the content of .config is influenced by the host as well,
like for the host gcc version, so it is interesting to have the resultig
.config.

> >  .gitlab-ci.yml | 1 +
> >  1 file changed, 1 insertion(+)
> You forgot to duplicate the code to the .gitlab-ci.yml.in

Damned, indeed! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2017-12-20 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 21:25 [Buildroot] [PATCH] gitlab-ci: add .config to artefacts Yann E. MORIN
2017-12-19  1:59 ` Ricardo Martincoski
2017-12-20 13:15   ` Yann E. MORIN [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=20171220131523.GA21413@scaer \
    --to=yann.morin.1998@free.fr \
    --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