[RFC][PATCH] ci: Build in kas docker image

[RFC][PATCH] ci: Build in kas docker image

[Jan Kiszka]

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.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---

RFC because I only suspect that this script was no longer in use for the
Jenkin CI.

 .gitlab-ci.yml | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 43caaea..79a6710 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,8 +1,20 @@
+image: kasproject/kas-isar:latest
+
 all:
   stage: build
   script:
-    - ./scripts/ci_build.sh
-  artifacts:
-    paths:
-    - images/isar-image-base-qemuarm.ext4.img.gz
-    - images/isar-image-base.rpi-sdimg.gz
+    - export http_proxy=$HTTP_PROXY
+    - export https_proxy=$HTTPS_PROXY
+    - export ftp_proxy=$FTP_PROXY
+    - export no_proxy=$NO_PROXY
+    - source isar-init-build-env out
+    - bitbake
+        multiconfig:qemuarm-wheezy:isar-image-base
+        multiconfig:qemuarm-jessie:isar-image-base
+        multiconfig:qemuarm-stretch:isar-image-base
+        multiconfig:qemuarm64-stretch:isar-image-base
+        multiconfig:qemui386-jessie:isar-image-base
+        multiconfig:qemui386-stretch:isar-image-base
+        multiconfig:qemuamd64-jessie:isar-image-base
+        multiconfig:qemuamd64-stretch:isar-image-base
+        multiconfig:rpi-jessie:isar-image-base
-- 
2.13.6

Re: [RFC][PATCH] ci: Build in kas docker image

[Alexander Smirnov]

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?

Alex

Re: [RFC][PATCH] ci: Build in kas docker image

[Jan Kiszka]

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.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: [RFC][PATCH] ci: Build in kas docker image

[Alexander Smirnov]

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

Re: [RFC][PATCH] ci: Build in kas docker image

[Alexander Smirnov]

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.
> 

Applied, thanks!