From: Suhail Singh <suhailsingh247@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: <guix-science@gnu.org>, Romain GARBAGE <romain.garbage@inria.fr>
Subject: Re: Preliminary continuous integration support for Codeberg
Date: Fri, 13 Dec 2024 13:47:50 -0500 [thread overview]
Message-ID: <87o71fa089.fsf@gmail.com> (raw)
In-Reply-To: <875xnn1o18.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 13 Dec 2024 18:38:27 +0100")
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> Romain has now implemented Forgejo support in Cuirass² (Forgejo is the
> software behind Codeberg) and we deployed it³ earlier today at
> https://guix.bordeaux.inria.fr — we like to live on the bleeding edge.
>
> The good news is that guix.bordeaux.inria.fr has already had its first
> jobsets created from pull requests! 🥳 In the Codeberg web interface,
> all we had to do was to configure webhooks in the project settings
> (those of guix-science/guix-science{,-nonfree}).
>
> ...
>
> ² https://issues.guix.gnu.org/74769
> ³ https://gitlab.inria.fr/guix-hpc/sysadmin/-/commit/49a9179c6487b40e0eb2b02f5eedcf789c9427a1
Is my understanding correct that in order for a third-party channel to
make use of this, one needs to first configure a cuirass instance that's
aware of it?
Relatedly, is there an OCI container image with Guix installed that's
published on a registry such that it can be used within something like
Woodpecker-CI?
--
Suhail
next prev parent reply other threads:[~2024-12-13 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 17:38 Preliminary continuous integration support for Codeberg Ludovic Courtès
2024-12-13 18:47 ` Suhail Singh [this message]
2024-12-14 10:53 ` Ludovic Courtès
2024-12-14 18:04 ` Cayetano Santos
2024-12-14 18:08 ` Suhail Singh
2024-12-14 18:38 ` Cayetano Santos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o71fa089.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=guix-science@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=romain.garbage@inria.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).