From: Andrew Ammerlaan <andrewammerlaan@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: GURU project <guru@gentoo.org>
Subject: Re: [gentoo-project] utilizing GH functionality that Gentoo infra does not provide
Date: Mon, 4 Apr 2022 17:38:27 +0200 [thread overview]
Message-ID: <c4cb4350-d33a-2fea-2e54-5171b81a3140@gentoo.org> (raw)
In-Reply-To: <8ede3224-7b97-a4a8-0846-fd1eac513de6@gentoo.org>
On 31/03/2022 20:07, Maciej Barć wrote:
>
> On 3/31/22 6:43 PM, Michael Jones wrote:
>>
>>
>> On Thu, Mar 31, 2022 at 6:48 AM Maciej Barć <xgqt@gentoo.org
>> <mailto:xgqt@gentoo.org>> wrote:
>>
>> GURU already started experimenting with usage of GH's CI [1],
>> though I can't skip over a very irritating fact: GH seems to think
>> that
>> there is only one Linux-based OS ("runs-on: ubuntu-latest"). IMO it
>> would be better to run the CI on Gentoo's containers - which is
>> possible
>> with GitLab's CI.
>> Also, on GitLab we do not have to pull images from official Docker
>> registry [2].
>>
>>
>> Do you mean to imply that Github's CI doesn't support Linux other than
>> Ubuntu? Or do you mean instead that Github's CI only supports
>> non-Ubuntu as docker containers?
>>
>> An example of using a non-Ubuntu Linux container can be found here:
>> https://github.com/ninja-build/ninja/blob/25cdbae0ee1270a5c8dd6ba67696e29ad8076919/.github/workflows/linux.yml#L13
>> <https://github.com/ninja-build/ninja/blob/25cdbae0ee1270a5c8dd6ba67696e29ad8076919/.github/workflows/linux.yml#L13>
>
> Good to know, I think GURU's CI does not utilize that.
The ::guru (and ::sci) CI use the pkgcheck GitHub Action [1], very
useful if you want to quickly setup a CI in your ebuild repository. It
doesn't really matter which OS you run it on though. All it does is run
pkgcheck on a collection of ebuild files etc, it will do that just as
well in a Ubuntu container as in a Gentoo container.
Something that is on my wishlist is to replace this with something
similar to what we have in ::gentoo (I.e. a CI that not only runs
pkgcheck but also complains in #gentoo-guru and via email if it is
broken. Automating this means that I no longer have to do it manually :P)
Best regards,
Andrew
[1] https://github.com/pkgcore/pkgcheck-action
next prev parent reply other threads:[~2022-04-04 15:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:56 [gentoo-project] utilizing GH functionality that Gentoo infra does not provide Mike Frysinger
2022-03-29 18:26 ` Arthur Zamarin
2022-03-29 18:47 ` [gentoo-project] Gentoo's GitLab (was: utilizing GH functionality that Gentoo infra does not provide) Anna Vyalkova
2022-03-29 19:29 ` [gentoo-project] utilizing GH functionality that Gentoo infra does not provide Alec Warner
2022-03-31 2:01 ` Mike Frysinger
2022-03-29 19:36 ` Andreas K. Huettel
2022-03-31 2:01 ` Mike Frysinger
2022-03-31 8:21 ` David Seifert
2022-04-01 4:04 ` Mike Frysinger
2022-04-04 18:54 ` Andreas K. Huettel
2022-03-31 11:48 ` Maciej Barć
2022-03-31 16:43 ` Michael Jones
2022-03-31 18:07 ` Maciej Barć
2022-04-04 15:38 ` Andrew Ammerlaan [this message]
2022-04-01 1:27 ` Sam James
2022-04-01 1:28 ` Sam James
2022-04-01 4:29 ` Mike Frysinger
2022-04-01 4:17 ` Mike Frysinger
2022-04-01 5:52 ` Ulrich Mueller
2022-04-04 18:48 ` Andreas K. Huettel
2022-04-02 15:48 ` Matt Turner
2022-06-11 17:15 ` Luca Barbato
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=c4cb4350-d33a-2fea-2e54-5171b81a3140@gentoo.org \
--to=andrewammerlaan@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=guru@gentoo.org \
/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