From: "Maxim Yu. Osipov" <mosipov@isar-build.org>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/2] ci_build: Add signing cached repo test
Date: Tue, 27 Aug 2019 21:57:28 +0200 [thread overview]
Message-ID: <d30a35b9-db9f-7cea-c1ac-cacec16a5e92@isar-build.org> (raw)
In-Reply-To: <e7db9c00-7054-502f-7ac1-e7b1e4ee8e96@siemens.com>
On 8/27/19 9:05 AM, Jan Kiszka wrote:
<snip>
> On 27.08.19 08:43, Maxim Yu. Osipov wrote:
>
> BTW, do we consider -r -s as being part of a fast CI run? Then both
> should likely be added to .gitlab-ci.yml.
I fear that this will significantly increase the time of already time
consuming 'fast' build...
You are free to call ci_build with arguments '-f -r -s' if you need to
additionally test signing cached repo.
Thanks,
Maxim.
prev parent reply other threads:[~2019-08-27 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 6:43 Maxim Yu. Osipov
2019-08-27 6:43 ` [PATCH v2 2/2] doc/user_manual: Add reference to GPG tutorial Maxim Yu. Osipov
2019-08-27 7:05 ` [PATCH v2 1/2] ci_build: Add signing cached repo test Jan Kiszka
2019-08-27 19:57 ` Maxim Yu. Osipov [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=d30a35b9-db9f-7cea-c1ac-cacec16a5e92@isar-build.org \
--to=mosipov@isar-build.org \
--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