| Commit message (Expand) | Author | Age |
|---|
| * | Fix group-to-alist•••To not just append elements to the alist.
| Christopher Baines | 2019-12-16 |
| * | Move group-to-alist to the model utils module•••So it can be more widely used.
| Christopher Baines | 2019-12-16 |
| * | Show the possible failure reasons on the build page•••When the build status is "Failed (dependency)".
| Christopher Baines | 2019-12-16 |
| * | Add a function to find the builds required for a build that failed | Christopher Baines | 2019-12-16 |
| * | Link to the build pages from the derivation page | Christopher Baines | 2019-12-16 |
| * | Add a page for each build | Christopher Baines | 2019-12-16 |
| * | Split out select-build-by-build-server-and-derivation-file-name•••Create select-build-id-by-build-server-and-derivation-file-name, which just
returns the id, and then a variant that returns more fields for making a page
for each build.
| Christopher Baines | 2019-12-15 |
| * | Improve select-builds-with-context-by-derivation-file-name•••To find builds for equivalent derivations.
| Christopher Baines | 2019-12-15 |
| * | Add a builds page for a specific revision•••Like the /builds page, but filtered for a specific revision.
| Christopher Baines | 2019-12-14 |
| * | Extend select-build-stats to allow filtering by revision | Christopher Baines | 2019-12-14 |
| * | Break down the build stats by build server | Christopher Baines | 2019-12-14 |
| * | Drop the default number of results on the derivation outputs page•••To have it load quicker, but also because 100 results aren't necessary.
| Christopher Baines | 2019-12-14 |
| * | Add "Fixed output" to the options for Reproducibility status•••On the derivation outputs page, as some derivations are reproducible by
definition, so it's good to identify and exclude these.
| Christopher Baines | 2019-12-14 |
| * | Implement the reproducibility status filter•••On the derivation-outputs page.
| Christopher Baines | 2019-12-14 |
| * | Add a parameter to form-horizontal-control affect multiple values•••Previously, the behaviour was to accept multiple values, but enable just
allowing one value to be entered.
| Christopher Baines | 2019-12-14 |
| * | Improve the next page links on the revision pages•••To add or update the relevant query parameter, rather than replacing all the
query parameters with the new value.
| Christopher Baines | 2019-12-13 |
| * | Add a utility to help generate next page links | Christopher Baines | 2019-12-13 |
| * | Improve the select-build-stats function•••Account for equivalent derivations, rather than counting them as unknown.
| Christopher Baines | 2019-12-12 |
| * | Fix the select-derivations-with-no-known-build•••The equivalent_derivations table was an experiment that didn't work, so switch
to using the derivations_by_output_details_set table.
Also take the build server id as input, as this allows selecting derivations
which have no known build for the relevant build server.
| Christopher Baines | 2019-12-12 |
| * | Add options to the query-build-servers script•••So you can select to query specific build servers.
| Christopher Baines | 2019-12-12 |
| * | Remove non-existent export from the derivation module | Christopher Baines | 2019-12-12 |
| * | Add a page to show derivation outputs for a revision | Christopher Baines | 2019-12-12 |
| * | Add a function to select the outputs in a revision | Christopher Baines | 2019-12-12 |
| * | Add a results count to the revision derivations page | Christopher Baines | 2019-12-12 |
| * | Fix the all-results/limit handling in the revision derivatinos controller | Christopher Baines | 2019-12-12 |
| * | 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 Baines | 2019-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 Baines | 2019-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 Baines | 2019-12-12 |
| * | Add some database indexes | Christopher Baines | 2019-12-12 |
| * | Add a page to show the derivations in a revision | Christopher Baines | 2019-12-12 |
| * | Add a utility to generate a span for the status of a build | Christopher Baines | 2019-12-12 |
| * | Add a function to select derivations in a revision | Christopher Baines | 2019-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 Baines | 2019-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 Baines | 2019-12-12 |
| * | Display the build server URL when fetching data | Christopher Baines | 2019-12-12 |
| * | Fix the match statement in select-build-by-build-server-and… | Christopher Baines | 2019-12-12 |
| * | Improve variable names in fetch-narinfo-files | Christopher Baines | 2019-12-12 |
| * | Populate the narinfo_fetch_records table | Christopher Baines | 2019-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 Baines | 2019-12-12 |
| * | Change nar_urls size to bigint•••As some nars can be bigger than the size of an int.
| Christopher Baines | 2019-12-12 |
| * | Change nars size to bigint•••As some nars can be bigger than the maximum size of an int.
| Christopher Baines | 2019-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 Baines | 2019-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 Baines | 2019-12-12 |
| * | Move build-status helpers to the html-utils module | Christopher Baines | 2019-12-12 |
| * | Include nars on the output page | Christopher Baines | 2019-12-12 |
| * | Add a new page for the narinfos associated with an output | Christopher Baines | 2019-12-12 |
| * | Add a page for each signing key | Christopher Baines | 2019-12-12 |
| * | Add a new html-utils module•••To store code used for rendering HTML across multiple controllers.
| Christopher Baines | 2019-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 Baines | 2019-12-12 |
| * | Support querying builds by build servers | Christopher Baines | 2019-12-12 |