Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Add datastore-list-builds-for-output-and-system | Christopher Baines | 2020-07-04 |
| | |||
* | Add datastore-find-build-derivation-system | Christopher Baines | 2020-07-03 |
| | |||
* | Record what systems agents fetch builds for | Christopher Baines | 2020-07-03 |
| | | | | | This can then be used by allocators to avoid allocating builds to agents that they're never going to fetch. | ||
* | Add datastore-for-each-build | Christopher Baines | 2020-07-01 |
| | |||
* | Support storing when builds start | Christopher Baines | 2020-07-01 |
| | | | | | | | This isn't particularly accurate, what's actually being stored is the current time when the record is inserted in to the coordinator database, but that should happen just before the agent starts the build, so hopefully that's good enough. | ||
* | Add datastore-call-with-transaction | Christopher Baines | 2020-06-20 |
| | |||
* | Support showing blocking builds | Christopher Baines | 2020-05-22 |
| | | | | | This is useful to find builds that have failed, and in failing blocked other builds from being attempted. | ||
* | Report the number of unprocessed hook events | Christopher Baines | 2020-05-21 |
| | |||
* | Improve handling of submitting builds | Christopher Baines | 2020-05-19 |
| | | | | | | Don't always substitute the derivation, just fetch it if it doesn't exist in the database. Also just use the name of the derivation, only read it from the disk when it needs storing in the database. | ||
* | Replace datastore-fetch-input-builds-for-unprocessed-builds | Christopher Baines | 2020-05-10 |
| | | | | | | | It worked under some database conditions, but was very slow under others. Move more of the logic in to SQL in an attempt to make the allocator faster. This sort of works, but there were some advantages to the approach before the approach being replaced in this commit. | ||
* | Add datastore-fetch-unprocessed-builds-with-propagated-priorities | Christopher Baines | 2020-05-10 |
| | | | | To use with the derivation ordered allocator. | ||
* | Add datastore-fetch-input-builds-for-unprocessed-builds | Christopher Baines | 2020-05-10 |
| | | | | | This will be used by the derivation ordered allocator to find builds which can be performed. | ||
* | Rework the ensure-all-related-derivations-have-builds option | Christopher Baines | 2020-05-09 |
| | | | | | | | This was resulting in duplicate builds for the same output, as that's not what it was guarding against, but I think that was my intention... Anyway this should actually only result in builds being created for outputs that are required. | ||
* | Add datastore-list-builds-for-derivation-recursive-inputs | Christopher Baines | 2020-05-08 |
| | |||
* | Add sqlite datastore support for storing unprocessed hook events | Christopher Baines | 2020-05-08 |
| | |||
* | Add datastore-list-setup-failures-for-build | Christopher Baines | 2020-05-01 |
| | |||
* | Fix --update-database | Christopher Baines | 2020-04-28 |
| | |||
* | Start tracking the duration of a few datastore functions | Christopher Baines | 2020-04-28 |
| | |||
* | Add datastore-find-build-result | Christopher Baines | 2020-04-27 |
| | |||
* | Support listing processed builds | Christopher Baines | 2020-04-27 |
| | |||
* | Add datastore functions to get metrics | Christopher Baines | 2020-04-26 |
| | |||
* | Fix datastore-find-build-output | Christopher Baines | 2020-04-25 |
| | | | | | I don't think when was really working, the procedure was returning <undefined> when it shouldn't have been. | ||
* | Add datastore-list-related-derivations-with-no-build | Christopher Baines | 2020-04-25 |
| | | | | | Useful for finding out what derivations need to be built to ensure all related derivations have been built by the build coordinator. | ||
* | Add datastore-list-builds-for-derivation | Christopher Baines | 2020-04-25 |
| | |||
* | Add datastore-list-build-outputs | Christopher Baines | 2020-04-23 |
| | |||
* | Add datastore-find-derivation-system | Christopher Baines | 2020-04-23 |
| | |||
* | Re-work how the datastore module re-exports things | Christopher Baines | 2020-04-17 |
| | | | | | This seems to avoid all the warnings, and fix the broken merge-generics behaviour. | ||
* | Add datastore-fetch-setup-failures | Christopher Baines | 2020-04-13 |
| | |||
* | Add datastore methods for handling setup failures | Christopher Baines | 2020-04-13 |
| | |||
* | Add datastore-store-build-result | Christopher Baines | 2020-04-13 |
| | |||
* | Add datastore-find-build-output | Christopher Baines | 2020-04-13 |
| | |||
* | Add datastore functions to find builds and derivation outputs | Christopher Baines | 2020-04-13 |
| | |||
* | Add datastore-agent-for-build | Christopher Baines | 2020-04-13 |
| | | | | So that the coordinator can find out what agent is assigned a build. | ||
* | Support listing builds allocated for an agent | Christopher Baines | 2020-04-11 |
| | |||
* | Add allocation methods to the datastore | Christopher Baines | 2020-04-10 |
| | |||
* | Add sqlite datastore methods for allocating builds | Christopher Baines | 2020-04-10 |
| | |||
* | Add datastore-agent-password-exists? | Christopher Baines | 2020-04-10 |
| | |||
* | Implement finding agents | Christopher Baines | 2020-04-10 |
| | |||
* | Support creating passwords for agents | Christopher Baines | 2020-04-10 |
| | | | | | This should support generating the passwords off the value stored in the database, and the secret key base value, but that can be implemented later. | ||
* | Add the ability to list agents | Christopher Baines | 2020-04-10 |
| | |||
* | Support creating agents | Christopher Baines | 2020-04-10 |
| | | | | By running guix-build-coordinator agent new | ||
* | Implement storing builds | Christopher Baines | 2020-04-10 |
| | |||
* | Implement storing derivations | Christopher Baines | 2020-04-06 |