fix(ops/pipelines): Allow steps to run immediately after upload
This fix was recommended by Buildkite and is explained in the comment. Change-Id: I3f1c1c07cba0b417857d69c021c8af4750d645c4 Reviewed-on: https://cl.tvl.fyi/c/depot/+/4334 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org>
This commit is contained in:
parent
b6d143e5d2
commit
743bee8686
1 changed files with 11 additions and 0 deletions
|
@ -62,6 +62,17 @@ let
|
|||
# pipeline construction.
|
||||
(pathExists (unsafeDiscardStringContext target.outPath));
|
||||
in if shouldSkip then "Target was already built." else false;
|
||||
|
||||
# Add a "fake" dependency on the initial static pipeline step. When
|
||||
# uploading a pipeline dynamically, an implicit dependency on the uploading
|
||||
# step is added to all newly created build steps. Since we are uploading in
|
||||
# batches this stops the jobs in the first batch from running before all
|
||||
# batches have been uploaded.
|
||||
#
|
||||
# By setting an explicit dependency on a step that has always completed at
|
||||
# this point, we override that behaviour and allow the steps to start
|
||||
# running already.
|
||||
depends_on = ":init:";
|
||||
};
|
||||
|
||||
# Protobuf check step which validates that changes to .proto files
|
||||
|
|
Loading…
Reference in a new issue