aboutsummaryrefslogtreecommitdiff
path: root/guix-build-coordinator/hooks.scm
Commit message (Collapse)AuthorAge
* Add build-canceled-send-event-to-guix-data-service-hookChristopher Baines2020-12-21
|
* Add a hook for when builds are canceledChristopher Baines2020-12-21
|
* Fix default-build-missing-inputs-hookChristopher Baines2020-12-21
|
* Handle canceled builds in the default-build-missing-inputs-hookChristopher Baines2020-12-21
|
* Make the build-success-publish-hook behaviour more transactionalChristopher Baines2020-12-20
|
* Use the same skip if narinfo exists logic in the publish hookChristopher Baines2020-12-17
| | | | | As is used in the S3 publish hook. This is useful when you don't want to overwrite existing nar+narinfo entries.
* Avoid errors when derivation for missing input can't be foundChristopher Baines2020-12-04
| | | | I've seen this happen with derivation source files.
* Propagate build tags when inserting builds for missing inputsChristopher Baines2020-11-24
| | | | | | This is useful when using tags to track the origin of builds. This doesn't necessarily have to be mandatory, maybe there are some tags where propagating isn't helpful.
* Don't assume the missing input to a build is a direct inputChristopher Baines2020-10-24
| | | | | | | | | | | | Substitutes could be available for all direct inputs, but be missing for things they reference. This could happen if those builds happened on a machine with the store items available for example. Therefore, search the entire graph for the relevant derivation when looking for the derivation to build to provide the missing input. This change matches up with the similar improvement around handling fetching substitutes.
* Allow configuring the s3-publish-hook with a aws commandChristopher Baines2020-10-24
| | | | So that an absolute filename can be used.
* Move the post-publish-behaviour inside the s3 publish hookChristopher Baines2020-10-22
| | | | | | So that it'll run only if the narinfo on S3 is changed, because this should prevent it running when the hook wouldn't change the narinfo on S3, because one already exists.
* Support extending the S3 publish hookChristopher Baines2020-10-19
| | | | To allow doing things with the nar/narinfo files before they're deleted.
* Add a hook to recomress build log filesChristopher Baines2020-10-11
|
* Better describe the default hooksChristopher Baines2020-09-17
|
* Remove backtick that snuck inChristopher Baines2020-07-04
|
* Add hooks to send events to the Guix Data ServiceChristopher Baines2020-07-01
|
* Add a hook for when a build starts on an agentChristopher Baines2020-07-01
|
* Add a hook for when builds are submittedChristopher Baines2020-07-01
|
* Add a build failure hook to retry buildsChristopher Baines2020-05-23
|
* Start passing build-coordinator records to hooksChristopher Baines2020-05-08
| | | | | Plus more coordinator methods. This is a step towards making the allocator configurable.
* Add a hook for publishing to a S3 compatible endpointChristopher Baines2020-05-07
| | | | | | This is helpful if you don't have local storage for nars. There's nothing special about S3 beyond it's something I wanted to be able to use. I'm hoping to support other useful ways of publishing substitutes as well.
* Add a hook to generate the files needed to provide substitutesChristopher Baines2020-04-23
|
* Add a hook to handle missing inputsChristopher Baines2020-04-17
| | | | | | | That submits new build jobs to build these missing inputs if appropriate. This means that you can tell the coordinator to build something, and it will automatically attempt to build the dependencies if they're missing.
* Implement a couple of basic hooksChristopher Baines2020-04-16
This allows configurable code to be executed when builds succeed or fail.