all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: [GSoC] Rewrite Hydra to be more integrated with Guix.
Date: Thu, 17 Mar 2016 22:38:45 +0100	[thread overview]
Message-ID: <87bn6c944a.fsf@gnu.org> (raw)

Hello fellow Guix Hackers,

Being currently a student which is due to make an internship, I intend
to turn this boring administrative injunction into an opportunity to
contribute to Guix by applying to Google Summer of Code which is
considered as an internship by University of Bordeaux standards.

Hydra is a Nix-based continuous build system which is used by Guix to
compile packages on different platforms and to distribute packages
substitutes.  With time, nix-daemon and guix-daemon are evolving
differently.  Hydra being heavily dependent on nix-daemon, Guix is not
able to use its newest versions.  Moreover there are some software
related performance issues (among others) in the current Guix
infrastructure that are unlikely to be solved considering the
foreignness of Hydra Perl implementation to Guix hackers.

In that context, I am willing to work on implementing a continous build
system similar to Hydra in Guile.

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).

- Adding support for configuring and launching jobs remotely.

Everyone is welcome to provide its input in order to improve the roadmap
or commenting on the global picture.

I have added an entry for this project in the GSoC idea list:

  https://libreplanet.org/wiki/Group:Guix/GSoC-2016#Rewrite_Hydra_to_be_more_integrated_with_Guix

-- 
Mathieu Lirzin

             reply	other threads:[~2016-03-17 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 21:38 Mathieu Lirzin [this message]
2016-03-18  8:29 ` [GSoC] Rewrite Hydra to be more integrated with Guix Alex Kost
2016-03-18 20:55   ` Ludovic Courtès
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=87bn6c944a.fsf@gnu.org \
    --to=mthl@gnu.org \
    --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.