From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Phil <phil@beadling.co.uk>
Cc: guix-devel@gnu.org
Subject: Re: Guix+Jenkins slides/video
Date: Thu, 21 Oct 2021 21:21:44 +0200 [thread overview]
Message-ID: <87ee8eyyif.fsf@gnu.org> (raw)
In-Reply-To: <87ilydglnr.fsf@beadling.co.uk> (phil@beadling.co.uk's message of "Mon, 04 Oct 2021 10:54:32 +0100")
Hello!
Phil <phil@beadling.co.uk> skribis:
> A few of you might know me from guix-help or the Guix reddit channel.
>
> I did a talk last week and there's been some interest so thought I'd
> post the link here:
> https://www.devopsworld.com/agenda/session/617842
I discover this pretty late, the slides are insightful!
> Slides are available at the bottom without registration. The video
> requires registration (and needs full screen).
>
> This is still a work in progress, so any suggestions, comments,
> questions very welcome.
You mention functional overlap between Jenkins and Guix somewhere, and I
can see that, mostly when it comes with scheduling (the same sort of
problem shows up in Cuirass and in the Build Coordinator, mostly because
guix-daemon makes opaque scheduling/offloading decisions.)
The motivating example is interesting. Do you find that ‘guix pull’ and
‘guix time-machine’ serve you well for CI, or are they too slow?
Perhaps you pin the ‘guix’ channel?
> Current work is focusing on generating AWS Lambda functions in Jenkins
> using Guix profiles, and making Guix-Juptyer available on our Jenkins
> deployments - depending on progress we could offer to do talks at Guix
> Days 2021 on these.
Oh so you also use Guix-Jupyter? I’m interested in whatever feedback
you may have. :-)
Thanks for sharing!
Ludo’.
prev parent reply other threads:[~2021-10-21 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 9:54 Guix+Jenkins slides/video Phil
2021-10-11 10:36 ` zimoun
2021-10-15 6:59 ` Reza Housseini
2021-10-21 19:26 ` zimoun
2021-10-21 19:21 ` Ludovic Courtès [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
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=87ee8eyyif.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=phil@beadling.co.uk \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).