From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"Andreas J. Reichel" <andreas.reichel.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v7 0/5] Fix usage of additional apt keys and repos
Date: Wed, 20 Mar 2019 07:48:24 +0100 [thread overview]
Message-ID: <688943e7-4acc-94a1-810d-00f75fe6a070@ilbers.de> (raw)
In-Reply-To: <1d5477ce-2bf8-e734-c50a-6281c7d85959@siemens.com>
Hi Jan,
On 3/20/19 7:26 AM, Jan Kiszka wrote:
> On 19.03.19 22:58, Maxim Yu. Osipov wrote:
>> Hi Andreas,
>>
>> CI build ('scripts/ci_build.sh -q') failed. See
>> http://isar-build.org:8080/job/isar_mosipov_next/165/console
>>
>
> This is the same error I saw yesterday
> ("..isar-bootstrap-target/rootfs/dev: not mounted"). And given that this
> and my build had no overlap in our own patches, it must be something
> else you should examine because it may affect your patches
> (next..e13be9cefd87).
Yep, when I tested my patches CI build passed OK,
but now I see the same error in overnight build of 'next'.
>> We may create project for you on isar-build.org so you can run CI
>> build on isar-build.org before submitting patches to the mailing list.
>> We just need your github repo name (like
>> https://github.com/henning-schild-work/isar/)
>
> We rather need to find a way to make CI public, the current state is
> rather suboptimal. It's also not very well integrated with github.
>
> In fact, we need to find a way to build Isar in the cloud in general,
> also for use cases such as
> https://gitlab.com/cip-project/cip-core/isar-cip-core. And our internal
> CI is not scaling either. We do know how to do that better
> (container-based builds, controlled e.g. by gitlab-ci), but not yet how
> to deploy economically.
Agreed. To be honest I'm not a big fan of gitlab - it's rather slow.
Do you have any suggestions regarding other alternatives to gitlab/jenkins?
Maxim.
>
> 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:[~2019-03-20 6:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:35 Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 1/5] Revert "isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS" Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 2/5] Remove duplicate code from apt-keyring generation Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 3/5] Fix fetched key location in apt-keyring generator Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 4/5] Use apt-key to generate apt-keyring Andreas J. Reichel
2019-03-19 13:35 ` [PATCH v7 5/5] If we use a custom keyring debootstrap may fall to https Andreas J. Reichel
2019-03-19 13:36 ` [PATCH v7 0/5] Fix usage of additional apt keys and repos Andreas Reichel
2019-03-19 14:26 ` Maxim Yu. Osipov
2019-03-19 15:39 ` Andreas Reichel
2019-03-19 21:58 ` Maxim Yu. Osipov
2019-03-20 6:26 ` Jan Kiszka
2019-03-20 6:48 ` Maxim Yu. Osipov [this message]
2019-03-20 7:12 ` Jan Kiszka
2019-03-20 7:55 ` Maxim Yu. Osipov
2019-03-20 8:22 ` Jan Kiszka
2019-03-20 8:53 ` Maxim Yu. Osipov
2019-03-20 10:25 ` Andreas Reichel
2019-03-20 10:32 ` Maxim Yu. Osipov
2019-03-20 11:50 ` Andreas Reichel
2019-03-20 10:37 ` Jan Kiszka
2019-03-20 11:05 ` Maxim Yu. Osipov
2019-03-20 12:39 ` Jan Kiszka
2019-03-20 7:16 ` Claudius Heine
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=688943e7-4acc-94a1-810d-00f75fe6a070@ilbers.de \
--to=mosipov@ilbers.de \
--cc=andreas.reichel.ext@siemens.com \
--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