From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
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 14:25:37 +0300 [thread overview]
Message-ID: <539a43ca-166a-8ced-b6a5-548ffd7e2e90@ilbers.de> (raw)
In-Reply-To: <f8bfaf4c-c7ed-69ff-3f19-2f7f9a3093cd@siemens.com>
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
next prev parent reply other threads:[~2018-11-30 11:25 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 [this message]
2018-11-30 12:07 ` Jan Kiszka
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=539a43ca-166a-8ced-b6a5-548ffd7e2e90@ilbers.de \
--to=mosipov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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