unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Disarchive update
Date: Sun, 10 Oct 2021 15:22:29 +0200	[thread overview]
Message-ID: <87k0ilvwtm.fsf@gnu.org> (raw)
In-Reply-To: <87ee8u4h7v.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 09 Oct 2021 10:37:08 +0000")

Hi!

Mathieu Othacehe <othacehe@gnu.org> skribis:

>>   https://ci.guix.gnu.org/eval/29213?status=succeeded
>
> Nice! It looks like an expensive operation, maybe we should increase its
> period to 24 hours or so?

Yes, I’ve made it 12 hours now.  :-)

It shouldn’t be too expensive: there’s one derivation per tarball
disarchive and very few of them get rebuilt between subsequent
evaluations; disarchive-collection.drv depends on all of them.

However, I think the current model of Cuirass means that those
intermediate derivations aren’t retrieved on berlin so we’re potentially
building things multiple times?

>>   2. On berlin, add an mcron job that periodically copies the output of
>>      the latest “disarchive-collection” build to a directory, say
>>      /srv/disarchive.  Thus, the database would accumulate tarball
>>      metadata over time.
>
> We could add the result as a "build-product" so that it is available at:
> https://ci.guix.gnu.org/search/latest/disarchive-collection. The mcron
> job could use this URL to fetch the latest archive.

That’d be nice!  How do we do that again?

I was planning on retrieving the derivation file name in the mcron job
using the (guix ci) API, but having a build product may simplify things
a bit.

Thanks for your feedback!

Ludo’.


  reply	other threads:[~2021-10-10 13:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 10:05 Disarchive update Ludovic Courtès
2021-10-09 10:37 ` Mathieu Othacehe
2021-10-10 13:22   ` Ludovic Courtès [this message]
2021-10-12  8:41     ` Mathieu Othacehe
2021-10-14 14:06       ` Ludovic Courtès
2021-10-12  9:19 ` zimoun
2021-10-14 14:02   ` Ludovic Courtès
2021-10-14 19:17     ` zimoun
2021-10-21 19:41       ` Ludovic Courtès
2021-10-21 19:57         ` zimoun
2021-10-13 14:54 ` Timothy Sample
2021-10-14 14:04   ` Ludovic Courtès
2021-10-14 14:31 ` Ludovic Courtès
2021-10-14 21:44   ` zimoun
2021-10-21 19:44   ` Ludovic Courtès

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=87k0ilvwtm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@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).