diff options
| author | Christopher Baines <mail@cbaines.net> | 2020-01-04 09:43:04 +0000 |
|---|---|---|
| committer | Christopher Baines <mail@cbaines.net> | 2020-01-04 09:43:04 +0000 |
| commit | 4195cc3f7200527ae98d182babb266e97ea1bf8c (patch) | |
| tree | c58386f5fd894fb28c164664f69ac1d9ccd55ec7 /doc/cuirass.texi | |
| parent | 5c5790ad21d88599bb07dd9669708d8b58a47124 (diff) | |
| download | cuirass-4195cc3f7200527ae98d182babb266e97ea1bf8c.tar cuirass-4195cc3f7200527ae98d182babb266e97ea1bf8c.tar.gz | |
Support returning build information by output.support-returning-build-information-by-output
Being able to take a derivation and query the build information is useful, but
in cases where there are multiple derivations that produce the same outputs,
the probability of getting the data back from Cuirass is reduced.
This is because Cuirass might not have build the exact derivation you have,
but a different derivation that produces the same outputs (this can commonly
happen when a related fixed output derivation changes).
Cuirass doesn't store derivations if they produce the same outputs as a
derivation it already knows about, so it can't determine if this is the
case. Therefore, provide a way of querying build results by output, rather
than derivation.
The motivation behind this is to make it easier to import build information in
to the Guix Data Service.
* src/cuirass/database.scm (db-get-output): New procedure.
* src/cuirass/http.scm (respond-output-not-found): New procedure.
(request-path-components): Handle /output/… requests.
* doc/cuirass.texi (Build information): Mention that you can get build
information by output.
Diffstat (limited to 'doc/cuirass.texi')
| -rw-r--r-- | doc/cuirass.texi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/cuirass.texi b/doc/cuirass.texi index ebb1fa5..e652e8d 100644 --- a/doc/cuirass.texi +++ b/doc/cuirass.texi @@ -477,6 +477,10 @@ It is possible to query Cuirass web server for build informations. The dedicated API is "/build/@var{build-id}" where @var{build-id} is the unique id associated to the build in database. +The build information can also be queried by output. For example, +@samp{/output/kg9mirg6xbvzcp0a98v7326n1nvvwgsj-hello-2.10} will return +the details of the output, along with the build if available. + For instance, querying a local Cuirass web server can be done with @code{curl} and @code{jq} to format the JSON response : |