From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: ci_build.sh vs. ci_build.sh -f vs. gitlab-ci.yml
Date: Fri, 30 Nov 2018 13:07:35 +0100 [thread overview]
Message-ID: <efc90e6f-2015-92bc-b27b-95fd97c437b5@siemens.com> (raw)
In-Reply-To: <539a43ca-166a-8ced-b6a5-548ffd7e2e90@ilbers.de>
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
prev parent reply other threads:[~2018-11-30 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 10:37 Jan Kiszka
2018-11-30 11:25 ` Maxim Yu. Osipov
2018-11-30 12:07 ` Jan Kiszka [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=efc90e6f-2015-92bc-b27b-95fd97c437b5@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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