openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

fixing PV1, again

Browse Source
This commit is contained in:
Kathryn Alexander
2023-09-29 16:13:11 -04:00
committed by openshift-cherrypick-robot
parent 62bd682fe9
commit b3e00c8963
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cicd/index.adoc
View File

@@ -29,7 +29,7 @@ For more information, see xref:../cicd/builds/understanding-image-builds.adoc#un
== {pipelines-shortname}
{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.
For more information, see xref:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[Understanding {pipelines-shortname}].
For more information, see link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[Understanding {pipelines-shortname}].
[id="openshift-gitops"]
== OpenShift GitOps

4
cicd/jenkins/migrating-from-jenkins-to-openshift-pipelines.adoc
View File

@@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
You can migrate your CI/CD workflows from Jenkins to xref:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[{pipelines-title}], a cloud-native CI/CD experience based on the Tekton project.
You can migrate your CI/CD workflows from Jenkins to link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[{pipelines-title}], a cloud-native CI/CD experience based on the Tekton project.
include::modules/jt-comparison-of-jenkins-and-openshift-pipelines-concepts.adoc[leveloffset=+1]
@@ -23,5 +23,5 @@ include::modules/jt-examples-of-common-use-cases.adoc[leveloffset=+1]
[role="_additional-resources"]
== Additional resources
* xref:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[Understanding {pipelines-shortname}]
* link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[Understanding {pipelines-shortname}]
* xref:../../authentication/using-rbac.adoc#using-rbac[Role-based Access Control]

2
getting_started/openshift-overview.adoc
View File

@@ -56,7 +56,7 @@ to see your applications, monitor status, connect and group components, and modi
* ** xref:../cli_reference/odo-important-update.adoc#odo-important_update[Use the developer CLI tool (`odo`)]**:
The `odo` CLI tool lets developers create single or multi-component applications and automates deployment, build, and service route configurations. It abstracts complex Kubernetes and {product-title} concepts, allowing you to focus on developing your applications.
* **xref:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html#op-key-features[Create CI/CD Pipelines]**: Pipelines are serverless, cloud-native, continuous integration, and continuous deployment systems that run in isolated containers.
* **link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html#op-key-features[Create CI/CD Pipelines]**: Pipelines are serverless, cloud-native, continuous integration, and continuous deployment systems that run in isolated containers.
They use standard Tekton custom resources to automate deployments and are designed for decentralized teams working on microservices-based architecture.
* **Deploy Helm charts**: