From: "Ludovic Courtès" <ludo@gnu.org>
To: <guix-devel@gnu.org>
Subject: Cuirass 1.2.0 released
Date: Mon, 30 Oct 2023 17:42:27 +0100 [thread overview]
Message-ID: <87jzr42hak.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2711 bytes --]
Hello Guix!
It’s a bit of a non-event since we’ve been packaging and using snapshots
of Cuirass all along, but nevertheless, I’m totally thrilled to announce
that Cuirass 1.2.0 is out!
https://guix.gnu.org/en/cuirass/
Changes since 1.1.0 (excerpt from the ‘NEWS’ file):
** Core
*** Require Fibers >= 1.1.0
(<https://issues.guix.gnu.org/63389>)
*** Require Guile >= 3.0.6
*** Channels are always authenticated
*** Use a database connection pool instead of a worker thread
*** Now useless (cuirass watchdog) module has been removed
*** (cuirass database) now uses records instead of alists for data types
*** (cuirass base) rewritten as a set of actors
*** ‘cuirass register’ limits the number of concurrent evaluations
*** ‘cuirass register’ listens to ‘cuirass web’ on a “bridge” local socket
*** Keep GC roots for derivations that are queued
(<https://issues.guix.gnu.org/54447>)
*** Register a GC root for “build products”
(<https://issues.guix.gnu.org/64317>)
*** Logging level can be controlled with ‘CUIRASS_LOGGING_LEVEL’ env. variable
** Database
*** Allow specifications to be inactive
** Remote building
*** Worker stops requesting work when disk space is too low
*** Worker now asks for work as soon as it’s available
*** (cuirass remote) provides a higher-level interface for messages
*** ‘remote-worker’ and ‘remote-server’ are now a fiberized process
*** ‘remote-worker’ defines distributes available cores among workers
*** Fix memory corruption leading ‘remote-server’ to never reply
*** New ‘--log-expiry’ option for ‘cuirass remote-server’
*** Fix bug that would lead ‘remote-worker’ to wrongfully report failure
(<https://issues.guix.gnu.org/66692>)
*** ‘cuirass remote-worker’ periodically removes its own GC roots
** Web
*** Add /admin/specification/deactivate endpoint
*** Evaluation dashboard now supports filtering by build name
*** Evaluation dashboard shows completion time and commits
*** New /eval/latest?spec=… endpoint, linking to the latest dashboard
*** Evaluation page uncluttered
*** New /jobset/SPEC/hook/evaluation POST endpoint to trigger an evaluation
*** Build page provides hints for failed builds
*** Build page shows the build machine and/or worker ID
*** New /build/ID/log endpoint, with syntax-highlighted build logs
*** New ‘etc/new-client-cert.scm’ script; see “Authentication” in the manual
And guess what? 1.2.0 is already running at <https://ci.guix.gnu.org>.
Enjoy the colorful build logs and all that! :-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next reply other threads:[~2023-10-30 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:42 Ludovic Courtès [this message]
2023-10-31 15:49 ` Cuirass 1.2.0 released Katherine Cox-Buday
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=87jzr42hak.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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 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).