From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: FYI: Feasibility of CI on github
Date: Mon, 15 Feb 2021 14:45:12 +0100 [thread overview]
Message-ID: <ae975b0a-93e3-55e6-9192-7a68c8ce6032@siemens.com> (raw)
In-Reply-To: <20210215112728.GO20742@yssyq.m.ilbers.de>
On 15.02.21 12:27, Baurzhan Ismagulov wrote:
> On Fri, Feb 12, 2021 at 08:20:51PM +0100, Henning Schild wrote:
>> To get there we would need a CI system where the pipelines are part of
>> the code, so probably not jenkins.
>
> Just as a remark, Jenkins does support pipelines, we just don't use them; maybe
> I should prioritize that. We did resurrect our GitLab, and I don't see how it
> is better. Ideally, I want a different tool :) . In practice, many people use
> one of the two, so I'd be interested in documenting both workflows.
>
Either use github workflows, registering your runner as a private one
against the repo (and control who can trigger it, likely not PRs which
we don't do anyway). That way, CI would become publicly readable.
Gitlab is fine as well as long as the instance is on the Internet
(private one or gitlab.com). That's how we do it in Xenomai right now
(with private AWS runners sponsored by us).
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2021-02-15 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 12:53 Jan Kiszka
2021-02-12 9:16 ` Henning Schild
2021-02-12 10:01 ` Baurzhan Ismagulov
2021-02-12 10:28 ` Henning Schild
2021-02-12 10:53 ` Baurzhan Ismagulov
2021-02-12 16:55 ` Jan Kiszka
2021-02-15 11:30 ` Baurzhan Ismagulov
2021-02-12 19:20 ` Henning Schild
2021-02-15 11:27 ` Baurzhan Ismagulov
2021-02-15 13:45 ` Jan Kiszka [this message]
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=ae975b0a-93e3-55e6-9192-7a68c8ce6032@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