aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* WIP Add page to show derivation outputs for a revisionwip-rb6-summitChristopher Baines2019-12-08
|
* Add a function to select the outputs in a revisionChristopher Baines2019-12-08
|
* Add a results count to the revision derivations pageChristopher Baines2019-12-07
|
* Fix the all-results/limit handling in the revision derivatinos controllerChristopher Baines2019-12-07
|
* WIP speed up associating derivations with buildsChristopher Baines2019-12-07
|
* WIP add builds.derivation_output_details_set_idChristopher Baines2019-12-07
|
* WIP builds derivation_id REMOVE THIS CHANGEChristopher Baines2019-12-07
|
* WIP derivation output setsChristopher Baines2019-12-07
|
* Add some database indexesChristopher Baines2019-12-05
|
* Add a page to show the derivations in a revisionChristopher Baines2019-12-05
|
* Add a utility to generate a span for the status of a buildChristopher Baines2019-12-05
|
* Add a function to select derivations in a revisionChristopher Baines2019-12-05
|
* Fix and improve fetching outputs to fetch from build serversChristopher Baines2019-12-05
| | | | | | | | | | | The join on derivation_outputs was completely wrong, so fix that. Also, rather than only selecting outputs where there's a corresponding build, just eliminate outputs where there is an entry in the nars table, fetched from the relevant build server. Also just look at x86_64-linux derivations, because there's no filtering on relevant derivations for a build server at the moment.
* Fix query in select-derivations-with-no-known-buildChristopher Baines2019-12-05
| | | | | | | | | | | | | Rather than eliminating any derivation that has a known build, eliminate those derivations, but also equivalent derivations as well. For selecting the derivations in a revision, join on the equivalent derivations, as all the equilalent derivations need checking as well, as it's unknown which one Cuirass would have associated the build against. Also, filter for x86_64-linux, to avoid checking for crossbuilt things. This should be replaced by some way of describing what derivations a build server has.
* Display the build server URL when fetching dataChristopher Baines2019-12-05
|
* Fix the match statement in select-build-by-build-server-and…Christopher Baines2019-12-05
|
* Improve variable names in fetch-narinfo-filesChristopher Baines2019-12-05
|
* Populate the narinfo_fetch_records tableChristopher Baines2019-12-05
|
* WIP sort out deduplicate buildsChristopher Baines2019-12-05
|
* WIP Change nar_urls size to bigintChristopher Baines2019-12-05
|
* WIP change nars size to bigintChristopher Baines2019-12-05
|
* WIP equivalent derivationsChristopher Baines2019-12-05
|
* Add a table to record where narinfo files were fetched fromChristopher Baines2019-12-04
| | | | Otherwise it's hard to associated narinfo files to build servers.
* Add an index on the derivation_file_name field in the builds tableChristopher Baines2019-12-04
| | | | As this helps when finding builds relating to specific derivations.
* Move build-status helpers to the html-utils moduleChristopher Baines2019-12-03
|
* WIP include nars on the output pageChristopher Baines2019-12-02
|
* WIP add a new page for the narinfos associated with an outputChristopher Baines2019-12-02
|
* Add a page for each signing keyChristopher Baines2019-12-02
|
* Add a new html-utils moduleChristopher Baines2019-12-02
| | | | To store code used for rendering HTML across multiple controllers.
* Stop setting a long max-age for the viewing store itemsChristopher Baines2019-12-01
| | | | As as new derivations are loaded, the contents of the page can change.
* Support querying builds by build serversChristopher Baines2019-12-01
|
* Support querying builds by statusChristopher Baines2019-12-01
|
* Handle multiple invalid values for a single fieldChristopher Baines2019-12-01
|
* Query build servers for narinfo fileswip-narinfoChristopher Baines2019-11-30
| | | | | As well as making it possible to only query build servers for builds relating to a specific revision.
* Fix selecting pending buildsChristopher Baines2019-11-30
|
* Don't create misleading scheduled build status entriesChristopher Baines2019-11-30
| | | | | | | | Cuirass provides a timestamp field in build responses, and sometimes this means when the build was scheduled, but when the build is finished, it's the stoptime. So only use the timestamp when the build hasn't finished.
* Support handling jsonb in insert-missing-data-and-return-all-idsChristopher Baines2019-11-30
|
* Begin to add support for importing narinfo filesChristopher Baines2019-11-30
| | | | | This commit adds the tables, as well as code to support extracting data from narinfo files.
* Fix some queries relating to the build_status table changesChristopher Baines2019-11-28
|
* Fix the JSON output for the derivation history pageChristopher Baines2019-11-26
|
* Add the build-server-token-seed.scm file to Makefile.amChristopher Baines2019-11-26
|
* Extract the builds page in to it's own set of modulesChristopher Baines2019-11-24
| | | | To allow for expanding it, without cluttering the root controller.
* Respond to any method with a 404, if the request is unrecognisedChristopher Baines2019-11-24
|
* Just update the package derivation entries that need updatingChristopher Baines2019-11-24
| | | | | | | Previously, all the entries for the branch were deleted, but not, only the entries for the branch, that are present in the revision that was loaded will be deleted. This is more efficient, as it avoids deleting and recreating entries in the table that shouldn't have changed.
* Rework the builds and build_status tables as well as related codeChristopher Baines2019-11-24
| | | | | | | Allow for build status information to be submitted by POST request. This required some changes to the builds and build_status tables, as for example, the Cuirass build id may not be available, and the derivation may not be know yet, so just record the derivation file name.
* Add a script to help manage build serversChristopher Baines2019-11-23
| | | | | This computes and displays the tokens needed to send build events to the Guix Data Service.
* Add guile-gcrypt to the guix-dev.scm fileChristopher Baines2019-11-23
|
* Add a new module to handle build server token seedsChristopher Baines2019-11-23
| | | | | | | | | The intent with these tokens is for them to be provided when build events are submitted, preventing unauthorised submission of build events. It should be possible to make the database public, so it shouldn't contain any secret information. To have secret tokens that aren't in the database, store a token seed, and combine this with some secret data to compute the secret.
* Add new table to store token seeds for build serversChristopher Baines2019-11-23
|
* Improve select-build-servers to convert strings to appropriate typesChristopher Baines2019-11-23
|