public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [RFC][PATCH] ci: Build in kas docker image
Date: Mon, 26 Feb 2018 14:43:03 +0100	[thread overview]
Message-ID: <b38a417c-70c6-edd2-fef3-f03531f49ff8@siemens.com> (raw)

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

             reply	other threads:[~2018-02-26 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 13:43 Jan Kiszka [this message]
2018-03-02 12:37 ` Alexander Smirnov
2018-03-02 12:43   ` Jan Kiszka
2018-03-02 13:24     ` Alexander Smirnov
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=b38a417c-70c6-edd2-fef3-f03531f49ff8@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.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