Commit 4934c9d8 authored by Sarah Yasonik's avatar Sarah Yasonik Committed by Marcia Ramos

Include reference to deployment pipeline earlier

parent 8a6e141e
......@@ -49,7 +49,15 @@ Is it ok that some nodes have the new Rails version, but some nodes have the old
## A walkthrough of an update
Backwards compatibility problems during updates are often very subtle. This is why it is worth familiarizing yourself with [update instructions](../update/index.md), [reference architectures](../administration/reference_architectures/index.md), and [GitLab.com's architecture](https://about.gitlab.com/handbook/engineering/infrastructure/production/architecture/). But to illustrate how these problems arise, take a look at this example of a simple update.
Backward compatibility problems during updates are often very subtle. This is why it is worth
familiarizing yourself with:
- [Update instructions](../update/index.md)
- [Reference architectures](../administration/reference_architectures/index.md)
- [GitLab.com's architecture](https://about.gitlab.com/handbook/engineering/infrastructure/production/architecture/)
- [GitLab.com's upgrade pipeline](https://gitlab.com/gitlab-org/release/docs/blob/master/general/deploy/gitlab-com-deployer.md#upgrade-pipeline-default)
To illustrate how these problems arise, take a look at this example:
- 🚢 New version
- 🙂 Old version
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment