run pick-into-auto-deploy specs in parallel with package building
To speed up how often we deploy to staging for auto-deploy picks we discussed whether we could check for a passing build after the staging deploy as part of the QA stage.
[merges with green pipeline]
|
[the picker will pick into auto-deploy]
|
[the tagger will tag the latest on auto-deploy]
|
[omnibus builds]
|
[OPTION1: verify that CI passed for the gitlab sha]
|
[deploys to staging]
|
[QA + OPTION2: verify that CI passed for the gitlab sha]
|
[deploy to canary]
|
[QA]
|
[deploy to production]
- This will end up parallelizing the spec tests on what we are deploying, and the package+staging deploy.
- If we want to be more conservative we could also check for a passing build in the beginning of the deploy step, which may be just as good if the time to run specs is the same as the time to build the packages.
The change for this is probably fairly simple, we would disable the check for a green pipeline in the tagger, and enable a job in the deploy pipeline to validate we have a green pipeline during the staging deploy (before or after).
Incremental roll-out
-
Query how many auto-deploy branch pipelines are failing so we have an idea of this will result in a lot of aborted deployments -
Add a CI pipeline check to the beginning of the staging deploy, allow failures and only for auto-deploy builds -
If spec tests are taking longer than packages, we can move it to the end of the staging deploy
Edited by Alessio Caiazza