From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27876@debbugs.gnu.org
Subject: [bug#27876] [PATCH] cuirass: add Hydra compatible HTTP API.
Date: Tue, 01 Aug 2017 21:48:09 +0200 [thread overview]
Message-ID: <877eynnk7a.fsf@gmail.com> (raw)
In-Reply-To: <87ini84ptn.fsf@gnu.org>
Hi Ludo !
I'll submit a v2 soon, here are some answers to your remarks.
> That said, there’s only one place where we work, which is where we spawn
> the ‘evaluate’ command. It may be that spawning it with ‘open-pipe’
> from (ice-9 popen) would sidestep the problem because ‘open-pipe’ is
> specifically written to permit this.
The open-pipe solution seems fine indeed !
> I think it would be nice to have a couple of tests for the HTTP API.
> There are helpers in tests/publish.scm and (guix tests http) that could
> probably be borrowed here. WDYT?
Sure, I'll add some new tests on the new API.
> Anyway, awesome work! It’s a really important gap that you’re filling
> here.
Thank you ;)
> In the future it would be nice to have an API to add jobsets, trigger an
> evaluation, things like that. That’s probably more difficult though
> because we’ll need an authentication mechanism.
>
> Also we should consider Fiberizing the whole thing eventually, so that
> Cuirass can actually perform all its activities concurrently.
Yes my planning is the following :
1. Fiberizing the whole thing to make it scalable.
2. Add build start/stop detection : I think the ideal would be wip-ui
branch to get merged before, so that I can use the same mechanism to
parse build output :)
3. Add authentification, and the other API you're describing.
Still plenty of work !!
Mathieu
next prev parent reply other threads:[~2017-08-01 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 10:07 [bug#27876] [PATCH] cuirass: add Hydra compatible HTTP API Mathieu Othacehe
2017-07-31 14:57 ` Ludovic Courtès
2017-08-01 19:48 ` Mathieu Othacehe [this message]
2017-08-02 9:22 ` Ludovic Courtès
2017-08-01 19:51 ` [bug#27876] [PATCH v2 1/3] cuirass: Store new information in database to prepare new HTTP API integration Mathieu Othacehe
2017-08-01 19:51 ` [bug#27876] [PATCH v2 2/3] cuirass: add Hydra compatible HTTP API Mathieu Othacehe
2017-09-08 16:00 ` Ludovic Courtès
2017-08-01 19:51 ` [bug#27876] [PATCH v2 3/3] cuirass: Add tests for new " Mathieu Othacehe
2017-09-08 16:01 ` Ludovic Courtès
2017-09-08 15:59 ` [bug#27876] [PATCH v2 1/3] cuirass: Store new information in database to prepare new HTTP API integration Ludovic Courtès
2017-09-08 19:13 ` bug#27876: " Mathieu Othacehe
2017-09-08 20:44 ` [bug#27876] " Ludovic Courtès
2017-09-09 7:48 ` Mathieu Othacehe
2017-09-10 13:01 ` Ludovic Courtès
2017-09-10 13:26 ` Mathieu Othacehe
2017-09-10 20:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877eynnk7a.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=27876@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.