Skip to content
Snippets Groups Projects
Commit aaa0ffba authored by Jason Leasure's avatar Jason Leasure
Browse files

Merge branch 'julianthome/changelock-period' into 'main'

Document changelock periods and their impact on deployments

See merge request !42



Merged-by: default avatarJason Leasure <jleasure@gitlab.com>
Approved-by: default avatarJason Leasure <jleasure@gitlab.com>
Co-authored-by: default avatarJulian Thome <jthome@gitlab.com>
parents d01ae86d ddaca843
No related branches found
No related tags found
1 merge request!42Document changelock periods and their impact on deployments
Pipeline #1628283142 waiting for manual action
......@@ -44,6 +44,8 @@ service.
In case you wish to deploy from a branch, you can create a pipeline with the
environment variable `DEPLOY_BRANCH` set to `true`.
Keep in mind that project runway has [changelock periods](https://gitlab.com/gitlab-com/gl-infra/change-lock/blob/master/config/changelock.yml) in which redeployments to staging or productions are not possible. During changelock periods, the runway staging/production deployment jobs would fail with the error message `⚠️ ChangeLock check failed`. If this happens, we have to wait until the end of the changelog period and redeploy. This point is especially important when preparing security fixes because the [changelock periods](https://gitlab.com/gitlab-com/gl-infra/change-lock/blob/master/config/changelock.yml) could block their deployment.
## Using the Service
After the pipeline succeeded, you can access the service(s) through the
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment