From: Arun Isaac <arunisaac@systemreboot.net>
To: Olivier Dion <olivier.dion@polymtl.ca>, jgart <jgart@dismail.de>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: Arun Isaac Presentation on guix-forge this Saturday
Date: Thu, 26 May 2022 12:58:47 +0530 [thread overview]
Message-ID: <87a6b4oiq8.fsf@systemreboot.net> (raw)
In-Reply-To: <874k1dh02d.fsf@laura>
Hi Olivier,
> Tell me, does Laminar check for channels update like cuirass? The main
> feature I like about cuirass is that if any dependencies of a package is
> updated, it will rebuild my package. If it does support that, I will
> seriously consider switching to guix-forge for my project.
Short answer: No, laminar/guix-forge don't rerun CI jobs when package
dependencies change.
Long answer:
It should be possible to configure laminar to do something like that.
Laminar has a very minimalist Unix-philosophy design and does not even
automatically trigger CI jobs on git commits. The user has to manually
set up a post-receive hook in the git repository that runs `laminarc
queue <job-name>'. guix-forge automatically handles this post-receive
hook setup for you. So, though I don't immediately see how to do it, it
should be possible to set up something that runs `laminarc queue
<job-name>' on dependency changes.
Laminar stands out from other CI systems in that it is not a monolith
and is very easy to interface with external tools. So, I was able to
write up Guix system configuration to do it. But, if Cuirass can provide
smoother integration with Guix, I'm more than happy to switch. The main
blocker is the postgres database.
Regards,
Arun
next prev parent reply other threads:[~2022-05-26 8:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 23:26 Arun Isaac Presentation on guix-forge this Saturday jgart
2022-05-24 23:45 ` Tobias Geerinckx-Rice
2022-05-25 0:06 ` jgart
2022-05-25 6:29 ` Pjotr Prins
2022-05-25 7:27 ` Blake Shaw
2022-05-26 7:17 ` Arun Isaac
2022-05-30 15:55 ` Ludovic Courtès
2022-05-30 19:02 ` Arun Isaac
2022-05-30 19:31 ` jgart
2022-05-31 1:07 ` jgart
2022-08-16 12:25 ` Christine Lemmer-Webber
2022-05-25 9:07 ` zimoun
2022-05-25 16:25 ` jgart
2022-05-25 14:14 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-25 18:54 ` Arun Isaac
2022-05-25 19:41 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-26 7:28 ` Arun Isaac [this message]
2022-05-26 15:13 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-26 15:52 ` Arun Isaac
2022-05-27 9:06 ` Cuirass and SQL zimoun
2022-05-28 7:28 ` Blake Shaw
2022-05-28 8:45 ` Arun Isaac
2022-05-28 14:25 ` Ryan Prior
2022-05-28 15:30 ` Arun Isaac
2022-05-30 15:50 ` Ludovic Courtès
2022-05-30 19:12 ` Arun Isaac
2022-06-01 16:24 ` Ludovic Courtès
2022-05-28 18:01 ` jgart
2022-05-30 15:02 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-28 12:12 ` Arun Isaac Presentation on guix-forge this Saturday david larsson
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=87a6b4oiq8.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=olivier.dion@polymtl.ca \
/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).