Update a few redirected links
This commit is contained in:
parent
b31b6764ac
commit
27b0a870ec
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
redirect_to: 'https://design.gitlab.com/product-foundations/motion'
|
||||
redirect_to: 'https://design.gitlab.com/product-foundations/motion/'
|
||||
---
|
||||
|
||||
The content of this document was moved into the [GitLab Design System](https://design.gitlab.com/product-foundations/motion).
|
||||
The content of this document was moved into the [GitLab Design System](https://design.gitlab.com/product-foundations/motion/).
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
redirect_to: 'https://design.gitlab.com/product-foundations/illustration'
|
||||
redirect_to: 'https://design.gitlab.com/product-foundations/illustration/'
|
||||
---
|
||||
|
||||
The content of this document was moved into the [GitLab Design System](https://design.gitlab.com/product-foundations/illustration).
|
||||
The content of this document was moved into the [GitLab Design System](https://design.gitlab.com/product-foundations/illustration/).
|
||||
|
|
|
@ -6,7 +6,7 @@ type: concepts
|
|||
|
||||
Team Foundation Server (TFS), renamed [Azure DevOps Server](https://azure.microsoft.com/en-us/services/devops/server/)
|
||||
in 2019, is a set of tools developed by Microsoft which also includes
|
||||
[Team Foundation Version Control](https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/overview)
|
||||
[Team Foundation Version Control](https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/overview?view=azure-devops)
|
||||
(TFVC), a centralized version control system similar to Git.
|
||||
|
||||
In this document, we focus on the TFVC to Git migration.
|
||||
|
|
|
@ -17,8 +17,8 @@ systems.
|
|||
### Deploying Jaeger
|
||||
|
||||
To learn more about deploying Jaeger, read the official
|
||||
[Getting Started documentation](https://www.jaegertracing.io/docs/1.13/getting-started/).
|
||||
There is an easy to use [all-in-one Docker image](https://www.jaegertracing.io/docs/1.13/getting-started/#AllinoneDockerimage),
|
||||
[Getting Started documentation](https://www.jaegertracing.io/docs/latest/getting-started/).
|
||||
There is an easy to use [all-in-one Docker image](https://www.jaegertracing.io/docs/latest/getting-started/#AllinoneDockerimage),
|
||||
as well as deployment options for [Kubernetes](https://github.com/jaegertracing/jaeger-kubernetes)
|
||||
and [OpenShift](https://github.com/jaegertracing/jaeger-openshift).
|
||||
|
||||
|
@ -27,7 +27,7 @@ and [OpenShift](https://github.com/jaegertracing/jaeger-openshift).
|
|||
GitLab provides an easy way to open the Jaeger UI from within your project:
|
||||
|
||||
1. [Set up Jaeger](#deploying-jaeger) and configure your application using one of the
|
||||
[client libraries](https://www.jaegertracing.io/docs/1.13/client-libraries/).
|
||||
[client libraries](https://www.jaegertracing.io/docs/latest/client-libraries/).
|
||||
1. Navigate to your project's **Settings > Operations** and provide the Jaeger URL.
|
||||
1. Click **Save changes** for the changes to take effect.
|
||||
1. You can now visit **Operations > Tracing** in your project's sidebar and
|
||||
|
|
Loading…
Reference in New Issue