Migrates content from Using to Builders (#1111)

* Migrates content from Using to Builders

* Second commit for Github OAuth info

---------

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

builders_and_image_automation/master.adoc

@@ -5,29 +5,39 @@ include::modules/attributes.adoc[]
 = Builders and image automation
 :context: quay-builders-image-automation
 
+The following guide shows you how to configure the {productname} _builds_ feature on both bare metal and virtual machines. 
 
+include::modules/builds-overview.adoc[leveloffset=+1]
+include::modules/proc_use-quay-build-dockerfiles.adoc[leveloffset=+2]
+include::modules/configuring-openshift-tls-component-builds.adoc[leveloffset=+1]
 
-//need to be moved out in a future pr
-//docker files 
+//bare metal builders
 include::modules/proc_use-quay-build-workers-dockerfiles.adoc[leveloffset=+1]
-include::modules/proc_use-quay-build-dockerfiles.adoc[leveloffset=+1]
-
-//custom trigger
-include::modules/proc_use-quay-git-trigger.adoc[leveloffset=+2]
-
-//include::modules/proc_use-quay-skip-trigger.adoc[leveloffset=+1]
-
-//include::modules/proc_github-build-triggers.adoc[leveloffset=+1]
-
-
+include::modules/prepare-ocp-for-bare-metal-builds.adoc[leveloffset=+2]
+ifdef::upstream[]
+include::modules/setting-up-builds-aws.adoc[leveloffset=+3]
+endif::upstream[]
+include::modules/openshift-routes-limitations.adoc[leveloffset=+3]
 
 // Virtual builders
 include::modules/build-enhancements.adoc[leveloffset=+1]
-include::modules/build-enhanced-arch.adoc[leveloffset=+2]
-include::modules/build-limitations.adoc[leveloffset=+2]
 include::modules/builders-virtual-environment.adoc[leveloffset=+2]
+include::modules/red-hat-quay-s3-bucket-modify.adoc[leveloffset=+3]
+include::modules/red-hat-quay-gcp-bucket-modify.adoc[leveloffset=+3]
+
+//Starting a new build
+include::modules/starting-a-build.adoc[leveloffset=+1]
+
+//Build triggers with UI
+include::modules/build-trigger-overview.adoc[leveloffset=+1]
+include::modules/red-hat-quay-builders-ui.adoc[leveloffset=+2]
+include::modules/proc_use-quay-git-trigger.adoc[leveloffset=+3]
+include::modules/understanding-tag-naming-build-triggers.adoc[leveloffset=+3]
+include::modules/skipping-source-control-triggered-build.adoc[leveloffset=+3]
+include::modules/manually-triggering-a-build-trigger.adoc[leveloffset=+2]
 
+// Github OAUTH
+include::modules/proc_github-app.adoc[leveloffset=+1]
 
-//cosign
-//include::modules/cosign-oci-intro.adoc[leveloffset=+2]
-//include::modules/cosign-oci-with-quay.adoc[leveloffset=+2]
+//Troubleshooting
+include::modules/troubleshooting-builds.adoc[leveloffset=+1]

images/register-app.png

@@ -1,5 +1,14 @@
 :_content-type: PROCEDURE
 [id="red-hat-quay-builders-enhancement"]
-= {productname} build enhancements
+= Virtual builds with {productname-ocp}
 
-{productname} builds can be run on virtualized platforms. Backwards compatibility to run previous build configurations are also available. 
+_Virtual builds_ can be run on virtualized machines with {productname-ocp}. With this method, the _build manager_ first creates the `Job Object` resource. Then, the `Job Object` creates a pod using the `quay-builder-image`. The `quay-builder-image` contains the `quay-builder` binary and the Podman service. The created pod runs as `unprivileged`. The `quay-builder` binary then builds the image while communicating status and retrieving build information from the _build manager_.
+
+[id="quay-builds-limitations"]
+== Virtual builds limitations
+
+The following limitations apply to the _virtual builds_ feature:
+
+* Running _virtual builds_ with {productname-ocp} in an unprivileged context might cause some commands that were working under the previous build strategy to fail. Attempts to change the build strategy could potentially cause performance issues and reliability with the build.
+
+* Running _virtual builds_ directly in a container does not have the same isolation as using virtual machines. Changing the build environment might also cause builds that were previously working to fail. 

images/view-credentials.png

@@ -0,0 +1,5 @@
+:_content-type: CONCEPT
+[id="build-pre-configuration"]
+= Setting up {productname} builders with {ocp}
+
+You must pre-configure {productname-ocp} to allow the use of the _builder_ workers before using the _builds_ feature.

modules/build-enhancements.adoc

@@ -0,0 +1,7 @@
+:_content-type: PROCEDURE
+[id="build-trigger-overview"]
+= Build triggers
+
+_Build triggers_ are automated mechanisms that start a container image build when specific conditions are met, such as changes to source code, updates to dependencies, or link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/use_red_hat_quay/#webhook[creating a webhook call]. These triggers help automate the image-building process and ensure that the container images are always up-to-date without manual intervention.
+
+The following sections cover content related to creating a build trigger, tag naming conventions, how to skip a source control-triggered build, starting a _build_, or manually triggering a _build_.