Subject: [bug#32121] [PATCH 4/5] database: Call a specification 'jobset' instead of 'project'.

From: [email-masked] (Ludovic Courtès)
Date: Fri, 13 Jul 2018 10:51:16 +0200

Clément Lassieur <[email-masked]> skribis:

> This removes the possibility to filter specifications by branch, because
> branches were previously called 'jobset'.  But it doesn't matter because later
> on, specifications will have as many branches as inputs.  And people should
> filter by specification name instead.
>
> * doc/cuirass.texi (Build Information, Latest builds): Remove 'jobset',
> replace 'project' with 'jobset'.
> * src/cuirass/http.scm (build->hydra-build): Idem.
> * tests/database.scm (db-get-builds): Idem.
> * tests/http.scm (build-query-result, /api/latestbuilds?nr=1&jobset=guix,
> /api/latestbuilds?nr=1&jobset=gnu): Idem.
> * src/cuirass/database.scm (db-format-build, db-get-builds): Don't associate
> builds with branches (which were called 'jobset' afterwards).
> (db-get-builds): Remove the #:project filter.

To make sure I understand correctly: it’ll still be possible to have,
say, a “guix” job or a “modular” job built with several different
branches, right?

I think we should try to keep the HTTP API compatible with Hydra so we
don’t break guix-hydra.el and possibly Tatiana’s work.

WDYT?

Ludo’.