From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Adler, Michael (CT RDA IOT SES-DE)" <michael.adler@siemens.com>
Subject: Cloud setup for gitlab-ci isar runners
Date: Tue, 28 May 2019 19:53:12 +0200 [thread overview]
Message-ID: <2a243b9f-c30b-d736-b351-540c1b0ffd40@siemens.com> (raw)
Hi all,
as dropped in the middle of a thread already, my colleague Michael is working on
a project to spawn your own gitlab-ci runners on AWS (so far) that can build
Isar jobs [1] (and more, if you like). Today the first public build went green
[2], and there is now also a vivid discussion on the CIP mailing list about this
project and its potential [3][4].
Worth to look at it now for Isar's own use cases, I would say...
Jan
[1] https://gitlab.com/cip-playground/gitlab-cloud-ci
[2] https://gitlab.com/cip-project/cip-core/isar-cip-core/pipelines
[3] https://lists.cip-project.org/pipermail/cip-dev/2019-May/002371.html
[4] https://lists.cip-project.org/pipermail/cip-dev/2019-May/002389.html
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
reply other threads:[~2019-05-28 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2a243b9f-c30b-d736-b351-540c1b0ffd40@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=michael.adler@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