Skip to content

Commit 97c3caa

Browse files
authored
Merge pull request #85172 from mramendi/overview-fix-links
RHDEVDOCS 6257 update links in ci/cd overview
2 parents 085a1b4 + 59c83c4 commit 97c3caa

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

cicd/overview/index.adoc

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ OpenShift Builds provides you the following options to configure and run a build
2828

2929
* Builds using Shipwright is an extensible build framework based on the Shipwright project. You can use it to build container images on an {product-title} cluster. You can build container images from source code and Dockerfile by using image build tools, such as Source-to-Image (S2I) and Buildah.
3030
+
31-
For more information, see link:https://docs.openshift.com/builds/latest/about/overview-openshift-builds.html[Overview of Builds].
31+
For more information, see link:https://docs.redhat.com/en/documentation/builds_for_red_hat_openshift[builds for Red Hat OpenShift].
3232

3333
* Builds using `BuildConfig` objects is a declarative build process to create cloud-native apps. You can define the build process in a YAML file that you use to create a `BuildConfig` object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the `BuildConfig` object builds a runnable image and pushes the image to a container image registry. With the `BuildConfig` object, you can create a Docker, Source-to-image (S2I), or custom build.
3434
+
@@ -48,7 +48,7 @@ ifndef::openshift-dedicated,openshift-rosa[]
4848
== {pipelines-shortname}
4949
{pipelines-shortname} provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes.
5050

51-
For more information, see link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[Understanding {pipelines-shortname}].
51+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_pipelines[Red Hat OpenShift Pipelines].
5252
endif::openshift-dedicated,openshift-rosa[]
5353

5454
// This can be included in OSD and ROSA when the GitOps doc is ported.
@@ -57,9 +57,11 @@ ifndef::openshift-dedicated,openshift-rosa[]
5757
== OpenShift GitOps
5858
OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles.
5959

60-
For more information, see xref:../../cicd/gitops/about-redhat-openshift-gitops.adoc#about-redhat-openshift-gitops[About {gitops-title}].
60+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_gitops[Red Hat OpenShift GitOps].
6161
endif::openshift-dedicated,openshift-rosa[]
6262

6363
[id="jenkins-ci-cd"]
6464
== Jenkins
6565
Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the {product-title}. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart.
66+
67+
For more information, see xref:../../cicd/jenkins/images-other-jenkins.adoc#images-other-jenkins[Configuring Jenkins images].

0 commit comments

Comments
 (0)