[Buildroot] [PATCH] gitlab-ci: add .config to artefacts

[Buildroot] [PATCH] gitlab-ci: add .config to artefacts

[Yann E. MORIN]

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.

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>
---
 .gitlab-ci.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 691669f7f1..32f6d7d224 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -61,6 +61,7 @@ check-package:
         expire_in: 2 weeks
         paths:
             - test-output/*.log
+            - test-output/*/.config
             - test-output/*/images/*
 acmesystems_aria_g25_128mb_defconfig: *defconfig
 acmesystems_aria_g25_256mb_defconfig: *defconfig
-- 
2.11.0

[Buildroot] [PATCH] gitlab-ci: add .config to artefacts

[Ricardo Martincoski]

Hello,

On Mon, Dec 18, 2017 at 07:25 PM, Yann E. MORIN wrote:

s/artefacts/artifacts/g in the subject.

> 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.

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

[snip]
> ---
>  .gitlab-ci.yml | 1 +
>  1 file changed, 1 insertion(+)

You forgot to duplicate the code to the .gitlab-ci.yml.in

Regards,
Ricardo

[Buildroot] [PATCH] gitlab-ci: add .config to artefacts

[Yann E. MORIN]

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.  |
'------------------------------^-------^------------------^--------------------'