ci_build.sh vs. ci_build.sh -f vs. gitlab-ci.yml

ci_build.sh vs. ci_build.sh -f vs. gitlab-ci.yml

[Jan Kiszka]

Maksim,

I'd like to align gitlab-ci with ci_build.sh (because the former is what I run 
after changes), but it seems there is some gap in the latter: We do not perform 
test like cache_base_repo in the "slow-path". Is one supposed to run both paths 
in a row for full build coverage?

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: ci_build.sh vs. ci_build.sh -f vs. gitlab-ci.yml

[Maxim Yu. Osipov]

Hi Jan,

Yes, at the moment "fast" differs from standard (a.k.a."slow") not only 
in number of configurations but also with features turned on 
(cross-compilation + local apt cache).

"slow" is run currently overnights, while "fast" is used for initial 
patch verification.

I plan to additionally include 'cross-compilation' and 'local apt cache' 
in "slow" after sorting out current urgent topics.

Thanks,
Maxim.


On 11/30/18 1:37 PM, Jan Kiszka wrote:
> Maksim,
> 
> I'd like to align gitlab-ci with ci_build.sh (because the former is what 
> I run after changes), but it seems there is some gap in the latter: We 
> do not perform test like cache_base_repo in the "slow-path". Is one 
> supposed to run both paths in a row for full build coverage?
> 
> Thanks,
> Jan
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

Re: ci_build.sh vs. ci_build.sh -f vs. gitlab-ci.yml

[Jan Kiszka]

On 30.11.18 12:25, Maxim Yu. Osipov wrote:
> Hi Jan,
> 
> Yes, at the moment "fast" differs from standard (a.k.a."slow") not only in 
> number of configurations but also with features turned on (cross-compilation + 
> local apt cache).
> 
> "slow" is run currently overnights, while "fast" is used for initial patch 
> verification.

Well, even gitlab-ci finishes here in 1:10h, although only two of the 10 targets 
(there is one more in ci_build.sh, apparently) are cross. That makes even a 
full-blown test reasonably fast for CI on our server (which is currently still a 
slow 8-core machine).

> 
> I plan to additionally include 'cross-compilation' and 'local apt cache' in 
> "slow" after sorting out current urgent topics.

Ok, thanks. And I would recommend to include at least one native build in the 
fast path as well. Then I will switch gitlab-ci to use that.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux