From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: FYI: Feasibility of CI on github
Date: Fri, 12 Feb 2021 10:16:47 +0100 [thread overview]
Message-ID: <20210212101647.69e6b7cd@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20f63dff-b266-24b9-4356-341d99782420@siemens.com>
Hi,
that is very good news. And the current CI is a total mess anyways. All
in one 6h job. Maybe someone will find the time to improve this with
something like bats or pytest. And rip out that Avocado stuff ... does
anyone even use this?
Henning
Am Tue, 9 Feb 2021 13:53:29 +0100
schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> Hi all,
>
> just a note: github workflows can theoratically host our CI as well
> [1]. In practice, though, we are constrained by its disk limit [2],
> likely also the job runtime limit (6h) for a full CI run. So, if we
> wanted to make use of this, splitting up the CI script into smaller
> steps would be needed.
>
> That you can build full isar images on github has been proven in [3]
> already.
>
> Jan
>
> [1]
> https://github.com/siemens/isar/commit/2340460507ebfffcbded835c9dff7c179cc9defc
> [2]
> https://github.com/siemens/isar/runs/1862634380?check_suite_focus=true#step:5:1712
> [3] https://github.com/siemens/meta-iot2050/actions
>
next prev parent reply other threads:[~2021-02-12 9:26 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 [this message]
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
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=20210212101647.69e6b7cd@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--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