Without this, even though all outputs will still be built, only the main
output (usually $out) store path gets printed by --print-out-paths. In
turn, this means that only the main output will get sent to attic for
caching.
In Lix's case, this was causing the following scenarios:
- builder1 builds build.aarch64-darwin.{out,dev,doc}
- builder1 only pushes .out to the caches
- builder2 attempts to build perlBindings.aarch64-darwin, which depends
on -dev from build.aarch64-darwin.
- builder2 needs to rebuild all of build.aarch64-darwin to get -dev.
Change-Id: I51f7e641f987eebcd65b3cd57c1f6b1bfbfebd32
If the builder is set up with an attic configuration (as is the case
since today on the Lix Buildkite builders), every Buildkite build step
attempts to push all their output store paths to attic so they can be
reused in later builds and/or in further steps being scheduled on
different builders.
Change-Id: Id102be66ede70c46ca8c34e1c929977edb4d5f57
the buildkite docs seem to be incomplete. `timed_out` is also a valid
failure state, but this isn't mentioned anywhere in the rest api docs
Change-Id: I1911dba2e87466215fbafb779dfe65c547fb41a4
The current version uses `exec` instead of running this as a script.
Change-Id: Iba99753ba556b1713e73255de49b4a5c54867cd5
Signed-off-by: Raito Bezarius <raito@lix.systems>
