You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM, running the release pipeline from not-master branch triggers a subset of steps in the main pipeline.
OTOH the artifacts produced are not reflecting the test operation and they end up polluting the nightly tags which instead should result from the full main pipeline run. The reason for this is that the release itself is only a final set of publishing step over a successful nightly build.
What
Fix the nightly group of release steps to actually tag and push to test release, test bump.sh space, test docker image tag.
Bump.sh daily space is renamed to nightly
New test space is created in bump.sh
A token to push to it is stored in the buildkite hooks
Acceptance
When building the release pipeline over a non-master branch:
### Changes
- Shrink the windows steps, moving the setup
- Make sure we fail when trying to rewrite cabal versions or release
tags
- Skip unnecessary steps when testing the release pipeline
- Use `TEST_RC` variable in the pushing artifacts steps to respect
nightly and test separation
### Issues
fix#4935fix#4895
Why
ATM, running the release pipeline from not-master branch triggers a subset of steps in the main pipeline.
OTOH the artifacts produced are not reflecting the test operation and they end up polluting the
nightly
tags which instead should result from the full main pipeline run. The reason for this is that the release itself is only a final set of publishing step over a successfulnightly
build.What
test
release,test
bump.sh space,test
docker image tag.daily
space is renamed tonightly
test
space is created in bump.shAcceptance
When building the release pipeline over a non-master branch:
Issues
#4917
The text was updated successfully, but these errors were encountered: