From: Mark H Weaver <mhw@netris.org>
To: Simon Tournier <zimon.toutoune@gmail.com>,
Jing Luo <jing@jing.rocks>, Guix Devel <guix-devel@gnu.org>
Cc: GNU Guix maintainers <guix-maintainers@gnu.org>,
guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html
Date: Tue, 12 Mar 2024 10:22:48 -0400 [thread overview]
Message-ID: <87edcf8r70.fsf@netris.org> (raw)
In-Reply-To: <8734t08vtt.fsf@gmail.com>
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> Well, I do not see if there is a reply. If no, sorry! If yes, I am
> just adding my own curiosity. :-)
>
> CC: guix-maintainers and guix-sysadmin
> CC: Mark Weaver
>
> On lun., 08 janv. 2024 at 13:19, Jing Luo <jing@jing.rocks> wrote:
>
>> I am Jing Luo, a new member from the GNU webmaster team. I noticed that
>> gnu.org has a page on "GNU Development Resources" [1], which has a
>> section about "Hydra: Continuous builds and portability testing". As I
>> know, Guix now uses Cuirass for CI. The text [1] has not been updated
>> since 2012. Would anyone on this list be interested in writing something
>> about Cuirass to replace the Hydra section? Or does anyone have other
>> ideas about this page? You can send an email to webmasters@gnu (plural!)
>> or just reply to me.
>>
>>
>> [1] https://www.gnu.org/software/devel.html
>
> AFAIK, Hydra is now down. IIRC, Mark was in charge. Mark?
Yes, our instance of Hydra was retired many years ago. I agree that it
makes sense to remove it from <https://www.gnu.org/software/devel.html>.
Thanks,
Mark
next prev parent reply other threads:[~2024-03-12 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 4:19 Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html Jing Luo
2024-03-08 17:41 ` Simon Tournier
2024-03-12 4:15 ` Jing Luo
2024-03-12 14:22 ` Mark H Weaver [this message]
2024-03-16 15:46 ` Jing Luo
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=87edcf8r70.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=jing@jing.rocks \
--cc=zimon.toutoune@gmail.com \
/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).