| Commit message (Expand) | Author | Age |
|---|
| * | Support tracking the end time of builds | Christopher Baines | 2020-07-01 |
| * | Support storing when builds start•••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.
| Christopher Baines | 2020-07-01 |
| * | Support storing when builds are created | Christopher Baines | 2020-07-01 |
| * | Support adding tags to builds | Christopher Baines | 2020-05-31 |
| * | Add some more indexes to speed up derivation ordered allocation | Christopher Baines | 2020-05-11 |
| * | Replace datastore-fetch-input-builds-for-unprocessed-builds•••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.
| Christopher Baines | 2020-05-10 |
| * | Add datastore-fetch-unprocessed-builds-with-propagated-priorities•••To use with the derivation ordered allocator.
| Christopher Baines | 2020-05-10 |
| * | Add sqlite datastore support for storing unprocessed hook events | Christopher Baines | 2020-05-08 |
| * | Add a couple of indexes that should speed up allocating builds | Christopher Baines | 2020-04-29 |
| * | Create an index on derivation_outputs.output•••This is important to speed up looking for derivations that provide an output,
that's used in the allocation process.
| Christopher Baines | 2020-04-28 |
| * | Send over some metadata from the agent for each output•••This will hopefully make it easier to create narinfo files for the outputs. I
think all of this information can be derived from the nar, but I'm not sure
how to do that, so maybe this can eventually be removed.
| Christopher Baines | 2020-04-23 |
| * | Add a new table to store setup_failures•••This is when a build was allocated to an agent, but the agent couldn't setup
the environment for the build. One failure I'm particularly thinking about is
where inputs to the derivation are missing, so add another table to store
them.
| Christopher Baines | 2020-04-13 |
| * | Add the build_results table | Christopher Baines | 2020-04-13 |
| * | Create tables for allocating builds•••One table to store which build is allocated to which agent, and another to
store a "plan" of allocations. For this plan, a build can be potentially
allocated to multiple agents, and which agent it will be allocated to depends
on which agent claims it first.
| Christopher Baines | 2020-04-10 |
| * | Add initial agent related tables | Christopher Baines | 2020-04-10 |
| * | Add a migration to create the builds table | Christopher Baines | 2020-04-10 |
| * | Add tables for derivations | Christopher Baines | 2020-04-04 |
| * | Add an initial migration | Christopher Baines | 2020-04-03 |
| * | Add sqitch conf and empty plan | Christopher Baines | 2020-04-03 |