all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Lars-Dominik Braun <lars@6xq.net>,  guix-devel@gnu.org
Subject: Re: I'm retiring (for a while); help needed
Date: Mon, 17 Jun 2024 15:38:24 +0200	[thread overview]
Message-ID: <87h6dr1ygf.fsf@elephly.net> (raw)
In-Reply-To: <87wmmn923w.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 17 Jun 2024 14:37:39 +0200")

Ludovic Courtès <ludo@gnu.org> writes:

>> The channel updaters are running on the berlin server, and the channel
>> packages are built by the build farm guix.bordeaux.inria.fr.
>
> Is there a document summarizing the setup: the repos involved, the
> services/periodic jobs running, etc.?

There is no such document.  Here's how it's set up:

ci.guix.gnu.org is installed and configured from the hydra/berlin.scm
code in the maintenance.git repository[1].
"hydra/modules/sysadmin/packages.scm" defines "guix-cran-scripts", which
is built from the contents of its dedicated repository[2].

This package is used in "hydra/modules/sysadmin/services.scm" to define
two service types: "guix-cran-service-type" and
"guix-bioc-service-type".  These extend the mcron service type to run
the "update.sh" script.  The script acts on /var/lib/guix-cran and
/var/lib/guix-bioc, the respective home directories of the guix-cran and
guix-bioc user accounts.  The result of running the update script for
CRAN and Bioconductor is a new commit for each of the repositories at
[3] and [4].

The script commits and pushes to these repositories.  This means that
those user accounts have been granted push access via SSH keys.  These
keys obviously must stay secret.

-- 
Ricardo

[1]: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/
[2]: https://github.com/guix-science/guix-cran-scripts.git
[3]: https://github.com/guix-science/guix-cran
[4]: https://github.com/guix-science/guix-bioc


      reply	other threads:[~2024-06-17 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  6:08 I'm retiring (for a while); help needed Ricardo Wurmus
2024-05-31  9:56 ` jbranso
2024-06-01 14:01   ` Ludovic Courtès
2024-06-07  8:05     ` Ricardo Wurmus
2024-06-17 12:39       ` pico.css in Cuirass Ludovic Courtès
2024-06-17 13:22         ` Ricardo Wurmus
2024-06-01 14:03 ` I'm retiring (for a while); help needed Ludovic Courtès
2024-06-04 16:43 ` Simon Tournier
2024-06-04 19:35   ` jbranso
2024-06-07  7:58   ` Ricardo Wurmus
2024-06-28 12:51     ` Laurent Gatto
2024-06-07  6:35 ` Lars-Dominik Braun
2024-06-07  8:00   ` Ricardo Wurmus
2024-06-17 12:37     ` Ludovic Courtès
2024-06-17 13:38       ` Ricardo Wurmus [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=87h6dr1ygf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.