all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [GSoC] Rewrite Hydra to be more integrated with Guix.
Date: Fri, 18 Mar 2016 21:55:04 +0100	[thread overview]
Message-ID: <87pourld5j.fsf@gnu.org> (raw)
In-Reply-To: <87y49gxk8i.fsf@gmail.com> (Alex Kost's message of "Fri, 18 Mar 2016 11:29:01 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Mathieu Lirzin (2016-03-18 00:38 +0300) wrote:

[...]

>> This GSoC will not likely succeed in implementing every features Hydra
>> is currently providing.  The objective is rather to create the basis
>> which will then allow further developpements to overcomes the present
>> difficulties.  To achieve this the following milestones (suggested by
>> Ludo) will be followed:
>>
>> - Implementing a simple loop pulling Guix Git repository and building
>>   every packages.
>>
>> - Adding a “job” abstraction to be able to build different Git branches.
>>
>> - Adding support for a database to keep track of the build results with
>>   their associated commit, derivation and output.
>>
>> - Adding a API over HTTP to get the build results remotely (ideally
>>   through an Emacs interface).
>
> I dream of a more feature-full API, as the current "M-x guix-hydra-…"
> stuff is not very useful.

What features do you have in mind?

Now is a good time to throw ideas at Mathieu!  ;-)

Ludo’.

  reply	other threads:[~2016-03-18 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 21:38 [GSoC] Rewrite Hydra to be more integrated with Guix Mathieu Lirzin
2016-03-18  8:29 ` Alex Kost
2016-03-18 20:55   ` Ludovic Courtès [this message]
2016-03-19  7:48     ` Alex Kost
2016-03-19 20:59       ` Ludovic Courtès
2016-03-18 21:02 ` Ludovic Courtès
2016-03-22 21:31 ` Andreas Enge
2016-03-23 14:08   ` 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=87pourld5j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --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 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.