This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
CI: trigger simnet master and wait for status #7899
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SimNet
pipeline only when "nightly" variable is passed via schedule against `master branch./maintain/chaosnet
as it's inSimNet
repo for a whileflaming-fir
deployment as it's no longer usedThere's one "but" with this CI triggering: if remote CI is stuck, this pipeline will hang in the running state until manually stopped.
Next stage will be passing the variable to SimNet CI. Variable will bear the container tag name. This will require some changes:
Due to
trigger:
limitations it's impossible to pass a custom variable.TLDR;
variables:
in GitLab, and the common workaround is passing it with artifactstrigger:
does not supportscript:
so the workaround with passing via artifacts won't workcurl
around itThat said, we've agreed with @s3krit that it won't hurt to substitute the current
substrate --version
~2.0.0-d3b1f2
"pinned" image tag with GitLab built-inCI_COMMIT_SHORT_SHA
.