aboutsummaryrefslogtreecommitdiff
Commit message (Expand)AuthorAge
* Fix related builds in select-derivations-in-revision•••Rather than just counting builds where the derivation matches, select builds based on the derivation outputs, which accounts for different but equivalent derivations. Christopher Baines2019-12-12
* Add new derivation_output_details_set_id column to the builds table•••As this will hopefully provide a faster way of associating derivations with builds. Christopher Baines2019-12-12
* Start storing and identifying sets of derivation outputs•••Derivations are effectively equivalent if they produce the same set of outputs, which is possible because of the equivalence of fixed output derivations. A fixed output derivation can be different, but equivalent, because it produces the same fixed output. To better allow tracking equivalent derivations, primarily to allow working out what derivations might correspond to a build, store the sets of derivation outputs, and which derivations they relate to. Christopher Baines2019-12-12
* Add some database indexesChristopher Baines2019-12-12
* Add a page to show the derivations in a revisionChristopher Baines2019-12-12
* Add a utility to generate a span for the status of a buildChristopher Baines2019-12-12
* Add a function to select derivations in a revisionChristopher Baines2019-12-12
* Fix and improve fetching outputs to fetch from build servers•••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. Christopher Baines2019-12-12
* Fix query in select-derivations-with-no-known-build•••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. Christopher Baines2019-12-12
* Display the build server URL when fetching dataChristopher Baines2019-12-12
* Fix the match statement in select-build-by-build-server-and…Christopher Baines2019-12-12
* Improve variable names in fetch-narinfo-filesChristopher Baines2019-12-12
* Populate the narinfo_fetch_records tableChristopher Baines2019-12-12
* Deduplicate builds and add a unique index•••Duplicate builds could creep in if the code to create them ran concurrently. I didn't exclude them initially, as I was unsure if there should be such a restriction, but at least for now, Cuirass builds map exactly to a single derivation, so use the same restriction here. Christopher Baines2019-12-12
* Change nar_urls size to bigint•••As some nars can be bigger than the size of an int. Christopher Baines2019-12-12
* Change nars size to bigint•••As some nars can be bigger than the maximum size of an int. Christopher Baines2019-12-12
* Add a table to record where narinfo files were fetched from•••Otherwise it's hard to associated narinfo files to build servers. Christopher Baines2019-12-12
* Add an index on the derivation_file_name field in the builds table•••As this helps when finding builds relating to specific derivations. Christopher Baines2019-12-12
* Move build-status helpers to the html-utils moduleChristopher Baines2019-12-12
* Include nars on the output pageChristopher Baines2019-12-12
* Add a new page for the narinfos associated with an outputChristopher Baines2019-12-12
* Add a page for each signing keyChristopher Baines2019-12-12
* Add a new html-utils module•••To store code used for rendering HTML across multiple controllers. Christopher Baines2019-12-12
* Stop setting a long max-age for the viewing store items•••As as new derivations are loaded, the contents of the page can change. Christopher Baines2019-12-12
* Support querying builds by build serversChristopher Baines2019-12-12
* Support querying builds by statusChristopher Baines2019-12-12
* Handle multiple invalid values for a single form fieldChristopher Baines2019-12-12
* Query build servers for narinfo files•••As well as making it possible to only query build servers for builds relating to a specific revision. wip-narinfoChristopher Baines2019-11-30
* Fix selecting pending buildsChristopher Baines2019-11-30
* Don't create misleading scheduled build status entries•••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. Christopher Baines2019-11-30
* Support handling jsonb in insert-missing-data-and-return-all-idsChristopher Baines2019-11-30
* Begin to add support for importing narinfo files•••This commit adds the tables, as well as code to support extracting data from narinfo files. Christopher Baines2019-11-30
* 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 modules•••To allow for expanding it, without cluttering the root controller. Christopher Baines2019-11-24
* Respond to any method with a 404, if the request is unrecognisedChristopher Baines2019-11-24
* Just update the package derivation entries that need updating•••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. Christopher Baines2019-11-24
* Rework the builds and build_status tables as well as related code•••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. Christopher Baines2019-11-24
* Add a script to help manage build servers•••This computes and displays the tokens needed to send build events to the Guix Data Service. Christopher Baines2019-11-23
* Add guile-gcrypt to the guix-dev.scm fileChristopher Baines2019-11-23
* Add a new module to handle build server token seeds•••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. Christopher Baines2019-11-23
* 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
* Add a page to render the channel news entries for a revisionChristopher Baines2019-11-22
* Expand compare by datetime output•••Include the commit and datetime for the revisions that were compared. Christopher Baines2019-11-21
* Include the datetime in select-guix-revision-for-branch-and-datetimeChristopher Baines2019-11-21
* Fix select-guix-revision-for-branch-and-datetime•••Flip the inequality and order, as this was picking the first revision after the datetime, rather than the last revision before it, which was the intention, as this should give you the revision on the branch, at the datetime. Christopher Baines2019-11-21
* Remove some peek statements that snuck inChristopher Baines2019-11-21
* Include news entries on the comparison pageChristopher Baines2019-11-21