| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
| |
This will hopefully provide a less expensive way of finding out if a scheduled
build is probably blocked by other builds failing or being canceled.
By working this out when the build events are recieved, it should be more
feasible to include information about whether builds are likely blocked or not
in various places (e.g. revision comparisons).
|
| |
|
|
|
|
|
| |
As the guix-data-service process seems to be using excessive amounts of
memory, and this will be useful to track it.
|
| |
|
| |
|
| |
|
|
|
|
| |
As this is a little clearer.
|
| |
|
|
|
|
|
|
| |
The build event information can now contain the derivation outputs, as well as
the name of the derivation. This allows the Guix Data Service to join builds
up with derivations, even if it doesn't know about the derivation being built.
|
|
|
|
|
|
|
|
|
| |
The server part of the guix-data-service doesn't work great as a guix service,
since it often fails to start if the migrations take any time at all.
To address this, start the server before running the migrations, and serve the
pages that work without the database, plus a general 503 response. Once the
migrations have completed, switch to the normal behaviour.
|
|
|
|
|
|
|
|
| |
This means you can query for derivations where builds exist or don't exist on
a given build server.
I think this will come in useful when submitting builds from a Guix Data
Service instance.
|
|
|
|
| |
Thanks to Tobias for reporting.
|
|
|
|
|
| |
When there's a target, render the heading neatly, and include the target
parameter in the URLs.
|
| |
|
| |
|
|
|
|
| |
As this is clearer.
|
|
|
|
|
| |
Remove the brackets from the values since this makes the set of values more
consistent, and don't display the no additional fields value on the page.
|
|
|
|
| |
Since this speeds up the response if you don't need the nar information.
|
|
|
|
|
| |
For the latest processed revision, this is useful for looking up which is the
latest processed revision.
|
| |
|
|
|
|
|
| |
This caused a problem viewing this derivation
/gnu/store/65r4488732qy6ilrh1ryb8xwmip1qnir-tklib-0.6.tar.gz?uuid=tklib-0-6.drv
|
|
|
|
|
|
| |
From the HTML and JSON responses, since this data isn't very useful, and the
query to collect the small amount which is displayed is very slow. This could
return at some point, but in a proper paginated form which isn't slow.
|
|
|
|
|
| |
Previously, it wouldn't pull the mime types out of the request properly, I
think it does a better job of that now.
|
|
|
|
|
|
|
|
|
|
| |
comparison.scm: return query data for derivation comparison as an alist,
instead of list.
html.scm: Access derivation differences data using assq-ref.
controller.scm: remove mapping for outputs/inputs/sources.
utils.scm: add group-to-alist/vector function.
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
|
|
|
|
|
| |
For many pages where previously the title was just "Guix Data Service".
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
|
|
|
| |
This removes the need to hardcode some values in the code.
|
| |
|
|
|
|
| |
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
|
|
|
|
|
| |
This might be useful for working out when a non-master branch contains a newer
version of a package, or someone has sent in a patch for a newer version
already.
|
|
|
|
| |
This should be useful for looking at when system tests break.
|
| |
|
|
|
|
|
| |
At least from the home page, this fixes links where the branch name contains a
/.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This means that these derivations are stored, even if a later part of the
process fails. Having the channel instance derivations stored might help work
out why the failure occurred, or better display information about it.
|
|
|
|
| |
As I want to remove the field from the database.
|
| |
|
|
|
|
| |
Also fix some general issues with the rendering.
|
|
|
|
|
| |
This should come in useful for testing patches, as you can see what system
tests are affected, and check the build status.
|
| |
|
| |
|
| |
|
|
|
|
| |
As it uses a transaction with a wider scope.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This finds all the fixed output derivations in the graph of packages. I'm
planning to use this to queue builds for these derivations on a regular basis,
to monitor when fixed output derivations break (as the thing they download has
disappeared for example).
|
| |
|