From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC][PATCH] ci: Build in kas docker image
Date: Fri, 2 Mar 2018 16:24:39 +0300 [thread overview]
Message-ID: <eebc2a32-d5fb-3dca-256d-c84f298d16c2@ilbers.de> (raw)
In-Reply-To: <fe8abc55-5e25-c32e-5e6f-a57fbf073e60@siemens.com>
On 03/02/2018 03:43 PM, Jan Kiszka wrote:
> On 2018-03-02 13:37, Alexander Smirnov wrote:
>> On 02/26/2018 04:43 PM, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> This models a gitlab CI build via the kas-isar docker image. That image
>>> provides a stable execution environment, resolving all currently
>>> required host-side dependencies for us.
>>>
>>> Change the build stage to run the CI tests directly, instead of falling
>>> back to the - by now - incompatible ci_build.sh script.
>>>
>>> Drop artifact deployment from the public CI setup for now. They were
>>> incomplete anyway, and they should be accompanied with an expiry date if
>>> they should be reintroduced.
>>>
>>
>> What is the way for me to test this change?
>
> Set up a runner with special privileges for the docker containers,
> namely "--cap-add=SYS_ADMIN --cap-add=MKNOD --privileged --device
> $(/sbin/losetup -f)". Should be
>
> docker_privileged: True
> docker_cap_add: [ "MKNOD","SYS_ADMIN" ]
> docker_devices: [ "$(/sbin/losetup -f)" ]
>
> in the CI runner syntax. We are currently playing with this, but the
> whole thing still needs VM encapsulation per job because, well, it runs
> with super-foo. Can send you the code.siemens.com links offlist if you
> are interested.
Sure, please send it. Apart from this, I have no other objections, do
you still consider it as RFC, or I could apply it?
Alex
next prev parent reply other threads:[~2018-03-02 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:43 Jan Kiszka
2018-03-02 12:37 ` Alexander Smirnov
2018-03-02 12:43 ` Jan Kiszka
2018-03-02 13:24 ` Alexander Smirnov [this message]
2018-03-02 14:24 ` Alexander Smirnov
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=eebc2a32-d5fb-3dca-256d-c84f298d16c2@ilbers.de \
--to=asmirnov@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