| Commit message (Expand) | Author | Age |
|---|
| * | Add copyright and license headers to a bunch of source files•••That were missing them.
| Christopher Baines | 2019-12-26 |
| * | Remove a rogue 1 from the (guix-data-service model nar) module | Christopher Baines | 2019-12-26 |
| * | Add a function to fetch references for derivations•••This replicates the store item references for the derivation, through looking
up the inputs which the derivation references, and also the sources.
| Christopher Baines | 2019-12-26 |
| * | Add a function to fetch a derivation by file name hash | Christopher Baines | 2019-12-26 |
| * | Use the returned file name in select-derivation-by-file-name•••They should be the same, but it seems more sensible to return the value from
the database.
| Christopher Baines | 2019-12-26 |
| * | Add a function serialize a derivation•••This effectively duplicates the behaviour in Guix for serializing derivations,
but this uses the database representation in the Guix Data Service, rather
than the records Guix uses.
| Christopher Baines | 2019-12-26 |
| * | Ensure output ordering for derivations is correct•••This affects the formatted derivation output.
| Christopher Baines | 2019-12-26 |
| * | Fix the representation of the fixed output derivation hashes•••Previously, they were nix-base32-string encoded, but the representation in the
derivations is base16, so it doesn't make sense to use a different
representation in the database.
Therefore, add some code that runs before the start of each job to convert the
data in the database. It was easier to do this in Guile with the existing
support for working with these bytevector representations. After some
migration period, the code for converting the old hashes can be removed.
| Christopher Baines | 2019-12-26 |
| * | Group derivation input outputs together by derivation•••Both in terms of the code fetching the data from the database, as well as the
formatted and detail outputs. This corrects an error in the formatted output
for derivations where inputs would be duplicated.
| Christopher Baines | 2019-12-26 |
| * | Fix the successful builds outputs query where there are no revisions•••As it was erroring before.
| Christopher Baines | 2019-12-26 |
| * | Fix the derivations list on the builds page | Christopher Baines | 2019-12-23 |
| * | Fix the unknown build counts on the builds pages | Christopher Baines | 2019-12-23 |
| * | Fix an error when updating the package derivation versions table | Christopher Baines | 2019-12-23 |
| * | Include builds on the derivation history page | Christopher Baines | 2019-12-22 |
| * | Add a function to rebuild the package_derivations_by_guix_revision•••At the moment, some data is missing, but this code will fix that.
| Christopher Baines | 2019-12-22 |
| * | Extract out some functions from update-package-derivations-table•••To allow these to be used independently.
| Christopher Baines | 2019-12-22 |
| * | Extract management of package_derivations_by_guix_revision_range•••... entries in to a separate module, to split the code up a little further.
| Christopher Baines | 2019-12-22 |
| * | Allow filtering the revision builds page by system | Christopher Baines | 2019-12-22 |
| * | Filter builds on the revision builds page by revision | Christopher Baines | 2019-12-22 |
| * | Ignore cross built derivations for the build stats | Christopher Baines | 2019-12-22 |
| * | Allow filtering by system and target on the derivation-outputs page•••So that this can match up with the package reproducibility page.
| Christopher Baines | 2019-12-16 |
| * | Fix matching equivalent derivations in another function | Christopher Baines | 2019-12-16 |
| * | Add a page with charts to show package reproducibility | Christopher Baines | 2019-12-16 |
| * | 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 |
| * | 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 |
| * | 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 |
| * | Implement the reproducibility status filter•••On the derivation-outputs page.
| Christopher Baines | 2019-12-14 |
| * | Improve the select-build-stats function•••Account for equivalent derivations, rather than counting them as unknown.
| Christopher Baines | 2019-12-12 |
| * | Remove non-existent export from the derivation module | Christopher Baines | 2019-12-12 |
| * | Add a function to select the outputs in a revision | 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 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 the match statement in select-build-by-build-server-and… | Christopher Baines | 2019-12-12 |
| * | Populate the narinfo_fetch_records table | 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 |
| * | Support querying builds by build servers | Christopher Baines | 2019-12-12 |
| * | Support querying builds by status | Christopher Baines | 2019-12-12 |
| * | Support handling jsonb in insert-missing-data-and-return-all-ids | Christopher Baines | 2019-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 Baines | 2019-11-30 |
| * | Fix some queries relating to the build_status table changes | Christopher Baines | 2019-11-28 |