From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lirzin Subject: Re: [GSoC] Continuous integration tool =?utf-8?Q?=C3=A0?= la Hydra. Date: Mon, 25 Jul 2016 02:30:10 +0200 Message-ID: <87vazueezx.fsf@gnu.org> References: <871t4ksk0n.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50597) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRTn1-0008Df-Uh for guix-devel@gnu.org; Sun, 24 Jul 2016 20:30:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRTmx-0000cB-CP for guix-devel@gnu.org; Sun, 24 Jul 2016 20:30:35 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43173) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRTmx-0000c7-8T for guix-devel@gnu.org; Sun, 24 Jul 2016 20:30:31 -0400 Received: from mek33-4-82-236-46-88.fbx.proxad.net ([82.236.46.88]:42190 helo=godel) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1bRTmw-0002Pp-Jv for guix-devel@gnu.org; Sun, 24 Jul 2016 20:30:30 -0400 In-Reply-To: <871t4ksk0n.fsf@gnu.org> (Mathieu Lirzin's message of "Sun, 29 May 2016 22:10:16 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel Hello Guix! Here is a third update on my GSoC project after the second month. As a reminder, Hydra (https://nixos.org/hydra/) is a Nix-based continuous build system which is used by Guix to compile packages on different platforms and to distribute packages substitutes. The aim of this project is to replace Hydra with a more integrated software written in Guile, named =E2=80=9CCuirass=E2=80=9D. Since my second update I have first fixed a major bug. When building different branches of Guix and evaluating package derivations the results were always the same. The issue was that the evaluations were happening in the same Guile process which does not play well with module changes. To fix that I have used a separate process + pipe to get the evaluation results. In the last update, I have introduced usage of SRFI-9 records for specifications, jobs, and builds. While they are nice to organize data, they have major drawbacks: - not flexible when you want to informally create a container. - require serialization when passing them throught pipes. For those reasons I have switched to good ol' alists, which are flexible, persistant, directly readable and don't require messing with load paths. The downside is of course that there is no compile time checks when manipulating data. As stated in my last update. I have been working on storing data in a database. For that I have decided to use Guile-sqlite3. The principal efforts have consist of using an external schema file and design it. I have come up with this, but this will likely evolve in the future: --8<---------------cut here---------------start------------->8--- CREATE TABLE Specifications ( id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, repo_name TEXT NOT NULL, url TEXT NOT NULL, load_path TEXT NOT NULL, file TEXT NOT NULL, proc TEXT NOT NULL, arguments TEXT NOT NULL, -- The following columns are optional. branch TEXT, tag TEXT, revision TEXT ); CREATE TABLE Evaluations ( derivation TEXT NOT NULL PRIMARY KEY, job_name TEXT NOT NULL, specification INTEGER NOT NULL, FOREIGN KEY (specification) REFERENCES Specifications (id) ); CREATE TABLE Builds ( id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, derivation TEXT NOT NULL, log TEXT NOT NULL, output TEXT, -- NULL if build failed FOREIGN KEY (derivation) REFERENCES Evaluations (derivation) ); --8<---------------cut here---------------end--------------->8--- The next step will be to continue improving the database communication, and start looking how to implement the HTTP API. For those willing to follow my work, a Git repository is available here: https://notabug.org/mthl/cuirass Everyone is of course welcome to provide any feedback. Thanks. --=20 Mathieu Lirzin