Merge pull request #65361 from shipsing/RHDEVDOCS-5484-update

Author: kcarmichael08

_topic_maps/_topic_map.yml

@@ -1869,7 +1869,13 @@ Distros: openshift-enterprise,openshift-origin,openshift-online
 Topics:
 - Name: CI/CD overview
   File: index
-- Name: Builds
+- Name: Builds using Shipwright
+  Dir: builds_using_shipwright
+  Distros: openshift-enterprise
+  Topics:
+  - Name: Overview of Builds
+    File: overview-openshift-builds
+- Name: Builds using BuildConfig
   Dir: builds
   Distros: openshift-enterprise,openshift-origin,openshift-online
   Topics:

cicd/builds_using_shipwright/_attributes

@@ -0,0 +1 @@
+../../_attributes/

cicd/builds_using_shipwright/images

@@ -0,0 +1 @@
+../../images/

cicd/builds_using_shipwright/modules

@@ -0,0 +1 @@
+../../modules/

cicd/builds_using_shipwright/overview-openshift-builds.adoc

@@ -0,0 +1,26 @@
+:_content-type: ASSEMBLY
+[id="overview-openshift-builds"]
+= Overview of Builds
+:context: overview-openshift-builds
+include::_attributes/common-attributes.adoc[]
+
+toc::[]
+
+
+Builds is an extensible build framework based on the link:https://shipwright.io/[Shipwright project], which you can use to build container images on an {product-title} cluster. You can build container images from source code and Dockerfiles by using image build tools, such as Source-to-Image (S2I) and Buildah. You can create and apply build resources, view logs of build runs, and manage builds in your {product-title} namespaces.
+
+Builds includes the following capabilities:
+
+* Standard Kubernetes-native API for building container images from source code and Dockerfiles
+* Support for Source-to-Image (S2I) and Buildah build strategies
+* Extensibility with your own custom build strategies
+* Execution of builds from source code in a local directory
+* Shipwright CLI for creating and viewing logs, and managing builds on the cluster
+* Integrated user experience with the *Developer* perspective of the {product-title} web console
+
+
+Builds consists of the following custom resources (CRs):
+
+* `Build`
+* `BuildStrategy` and `ClusterBuildStrategy`
+* `BuildRun`

cicd/builds_using_shipwright/snippets

@@ -0,0 +1 @@
+../../snippets/

cicd/index.adoc

@@ -15,14 +15,18 @@ toc::[]
 
 [id="openshift-builds"]
 == OpenShift Builds
-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.
-
-OpenShift Builds provides the following extensible support for build strategies:
-
-* Docker build
-* Source-to-image (S2I) build
-* Custom build
-
+OpenShift Builds provides you the following two options to configure and run a build:
+
+* Builds using Shipwright
++
+An extensible build framework based on the Shipwright project, which you can use 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.
++
+For more information, see link:https://docs.openshift.com/builds/latest/about/overview-openshift-builds.html[Overview of Builds].
+
+* Builds using BuildConfig
++
+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.
++
 For more information, see xref:../cicd/builds/understanding-image-builds.adoc#understanding-image-builds[Understanding image builds]
 
 [id="openshift-pipelines"]