From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: gnulib-tool.py speeds up continuous integrations
Date: Mon, 06 May 2024 01:23:25 +0200 [thread overview]
Message-ID: <10365684.dE46n4Xy2H@nimes> (raw)
gnulib-tool is used is many CI jobs. Just adding 'python3' to the
prerequisites of such a job makes it run faster. Here are the execution
times for a single run, before and after adding 'python3', for those
CIs that I maintain or co-maintain. In minutes and seconds.
Before After
https://gitlab.com/gnulib/gnulib-ci/-/pipelines 30: 11:
https://gitlab.com/gnu-gettext/ci-distcheck/-/pipelines 36: 32:
https://gitlab.com/gnu-poke/ci-distcheck/-/pipelines 18:40 18:24
https://gitlab.com/gnu-libunistring/ci-distcheck/-/pipelines 11:25 09:16
https://gitlab.com/gnu-diffutils/ci-distcheck/-/pipelines 07:21 06:27
https://gitlab.com/gnu-grep/ci-distcheck/-/pipelines 06:51 06:08
https://gitlab.com/gnu-m4/ci-distcheck/-/pipelines 06:46 05:44
https://gitlab.com/gnu-sed/ci-distcheck/-/pipelines 05:28 04:39
https://gitlab.com/gnu-gzip/ci-distcheck/-/pipelines 04:16 03:58
https://gitlab.com/gnu-libffcall/ci-distcheck/-/pipelines 01:50 01:42
https://gitlab.com/gnu-libsigsegv/ci-distcheck/-/pipelines 00:45 00:42
Bruno
next reply other threads:[~2024-05-05 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 23:23 Bruno Haible [this message]
2024-05-06 15:49 ` gnulib-tool.py speeds up continuous integrations Simon Josefsson via Gnulib discussion list
2024-05-06 16:09 ` Simon Josefsson via Gnulib discussion list
2024-05-06 17:06 ` continuous integrations pipeline frameworks Bruno Haible
2024-05-06 17:34 ` Simon Josefsson via Gnulib discussion list
2024-05-06 16:54 ` continuous integrations Bruno Haible
2024-05-06 17:27 ` Simon Josefsson via Gnulib discussion list
2024-05-06 18:04 ` Bruno Haible
2024-05-11 15:20 ` continuous integrations — own runners Bruno Haible
2024-05-11 16:15 ` Simon Josefsson via Gnulib discussion list
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10365684.dE46n4Xy2H@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@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.
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).