Skip to content

Commit d5b3b08

Browse files
authored
Merge pull request #44137 from darshan-nagaraj/OSDOCS-2562
Adds CI/CD overview page
2 parents b7995d7 + ae3e4f4 commit d5b3b08

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1514,6 +1514,8 @@ Name: CI/CD
15141514
Dir: cicd
15151515
Distros: openshift-enterprise,openshift-origin,openshift-online
15161516
Topics:
1517+
- Name: CI/CD overview
1518+
File: index
15171519
- Name: Builds
15181520
Dir: builds
15191521
Distros: openshift-enterprise,openshift-origin,openshift-online

cicd/index.adoc

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
:_content-type: ASSEMBLY
2+
[id="ci-cd-overview"]
3+
= {product-title} CI/CD overview
4+
include::_attributes/common-attributes.adoc[]
5+
:context: ci-cd-overview
6+
7+
toc::[]
8+
9+
10+
{product-title} is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the {product-title} provides the following CI/CD solutions:
11+
12+
* OpenShift Builds
13+
* OpenShift Pipelines
14+
* OpenShift GitOps
15+
16+
[id="openshift-builds"]
17+
== OpenShift Builds
18+
With OpenShift Builds, you can create cloud-native apps by using a declarative build process. 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 typically builds a runnable image and pushes it to a container image registry.
19+
20+
OpenShift Builds provides the following extensible support for build strategies:
21+
22+
* Docker build
23+
* Source-to-image (S2I) build
24+
* Custom build
25+
26+
For more information, see xref:../cicd/builds/understanding-image-builds.adoc#understanding-image-builds[Understanding image builds]
27+
28+
[id="openshift-pipelines"]
29+
== OpenShift Pipelines
30+
OpenShift Pipelines 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.
31+
32+
For more information, see xref:../cicd/pipelines/understanding-openshift-pipelines.adoc#understanding-openshift-pipelines[Understanding OpenShift Pipelines]
33+
34+
[id="openshift-gitops"]
35+
== OpenShift GitOps
36+
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.
37+
38+
For more information, see xref:../cicd/gitops/understanding-openshift-gitops.adoc#understanding-openshift-gitops[Understanding OpenShift GitOps]
39+
40+
[id="jenkins-ci-cd"]
41+
== Jenkins
42+
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.

0 commit comments

Comments
 (0)