aboutsummaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2020-01-04 09:43:04 +0000
committerChristopher Baines <mail@cbaines.net>2020-01-16 08:33:03 +0000
commit46f73b6b7c05389c67b02d32c8946ca665611cba (patch)
treed6898d83986862907ee159866a2c3154f63efcb6 /COPYING
parent267649c9f0ade7728bb622ce9565a2a8af7e1db0 (diff)
downloadcuirass-46f73b6b7c05389c67b02d32c8946ca665611cba.tar
cuirass-46f73b6b7c05389c67b02d32c8946ca665611cba.tar.gz
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 'COPYING')
0 files changed, 0 insertions, 0 deletions