RHDEVDOCS-3856 Establish Jenkins category under the CI/CD

Author: rolfedh

_artifacts/toc.yml

@@ -1131,10 +1131,6 @@ main-menu:
             path: cicd/builds/troubleshooting-builds.adoc
           - name: Setting up additional trusted certificate authorities for builds
             path: cicd/builds/setting-up-trusted-ca.adoc
-      - name: Migrating from Jenkins to Tekton
-        items:
-          - name: Migrating from Jenkins to Tekton
-            path: cicd/jenkins-tekton/migrating-from-jenkins-to-tekton.adoc
       - name: Pipelines
         items:
           - name: Red Hat OpenShift Pipelines release notes
@@ -1183,6 +1179,13 @@ main-menu:
             path: cicd/gitops/configuring-sso-for-argo-cd-using-keycloak.adoc
           - name: Running GitOps control plane workloads on infrastructure nodes
             path: cicd/gitops/run-gitops-control-plane-workload-on-infra-nodes.adoc
+      - Name: Jenkins
+        Dir: jenkins
+        Distros: openshift-enterprise
+        Topics:
+        - Name: Migrating from Jenkins to OpenShift Pipelines
+          File: migrating-from-jenkins-to-openshift-pipelines
+
   - name: Images
     items:
       - name: Overview of images

_topic_maps/_topic_map.yml

@@ -1556,12 +1556,6 @@ Topics:
   - Name: Setting up additional trusted certificate authorities for builds
     File: setting-up-trusted-ca
     Distros: openshift-enterprise,openshift-origin
-- Name: Migrating from Jenkins to Tekton
-  Dir: jenkins-tekton
-  Distros: openshift-enterprise
-  Topics:
-  - Name: Migrating from Jenkins to Tekton
-    File: migrating-from-jenkins-to-tekton
 - Name: Pipelines
   Dir: pipelines
   Distros: openshift-enterprise
@@ -1609,7 +1603,7 @@ Topics:
   - Name: Deploying a Spring Boot application with Argo CD
     File: deploying-a-spring-boot-application-with-argo-cd
   - Name: Argo CD custom resource properties
-    File: argo-cd-custom-resource-properties  
+    File: argo-cd-custom-resource-properties
   - Name: Monitoring application health status
     File: health-information-for-resources-deployment
   - Name: Configuring SSO for Argo CD using Dex
@@ -1618,6 +1612,13 @@ Topics:
     File: configuring-sso-for-argo-cd-using-keycloak
   - Name: Running Control Plane Workloads on Infra nodes
     File: run-gitops-control-plane-workload-on-infra-nodes
+- Name: Jenkins
+  Dir: jenkins
+  Distros: openshift-enterprise
+  Topics:
+  - Name: Migrating from Jenkins to OpenShift Pipelines
+    File: migrating-from-jenkins-to-openshift-pipelines
+
 ---
 Name: Images
 Dir: openshift_images

cicd/jenkins-tekton/migrating-from-jenkins-to-tekton.adoc

@@ -0,0 +1,27 @@
+:_content-type: ASSEMBLY
+//Jenkins-Tekton-Migration
+[id="migrating-from-jenkins-to-openshift-pipelines_{context}"]
+= Migrating from Jenkins to OpenShift Pipelines or Tekton
+include::_attributes/common-attributes.adoc[]
+:context: migrating-from-jenkins-to-openshift-pipelines
+
+toc::[]
+
+You can migrate your CI/CD workflows from Jenkins to xref:../../cicd/pipelines/understanding-openshift-pipelines.adoc#understanding-openshift-pipelines[Red Hat OpenShift Pipelines], a cloud-native CI/CD experience based on the Tekton project.
+
+include::modules/jt-comparison-of-jenkins-and-openshift-pipelines-concepts.adoc[leveloffset=+1]
+
+include::modules/jt-migrating-a-sample-pipeline-from-jenkins-to-openshift-pipelines.adoc[leveloffset=+1]
+
+include::modules/jt-migrating-from-jenkins-plugins-to-openshift-pipelines-hub-tasks.adoc[leveloffset=+1]
+
+include::modules/jt-extending-openshift-pipelines-capabilities-using-custom-tasks-and-scripts.adoc[leveloffset=+1]
+
+include::modules/jt-comparison-of-jenkins-openshift-pipelines-execution-models.adoc[leveloffset=+1]
+
+include::modules/jt-examples-of-common-use-cases.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+== Additional resources
+* xref:../../cicd/pipelines/understanding-openshift-pipelines.adoc#understanding-openshift-pipelines[Understanding OpenShift Pipelines]
+* xref:../../authentication/using-rbac.adoc#using-rbac[Role-based Access Control]

cicd/jenkins-tekton/_attributes cicd/jenkins/_attributescicd/jenkins-tekton/_attributes renamed to cicd/jenkins/_attributes

@@ -1,22 +1,23 @@
 // Module included in the following assembly:
 //
-// jenkins-tekton/migrating-from-jenkins-to-tekton.adoc
+// jenkins/migrating-from-jenkins-to-openshift-pipelines.adoc
 
-[id="jt-comparison-of-jenkins-and-tekton-concepts_{context}"]
-= Comparison of Jenkins and Tekton concepts
+:_content-type: CONCEPT
+[id="jt-comparison-of-jenkins-and-openshift-pipelines-concepts_{context}"]
+= Comparison of Jenkins and OpenShift Pipelines concepts
 
-This section summarizes the basic terms used in Jenkins and Tekton, and compares the equivalent terms.
+You can review and compare the following equivalent terms used in Jenkins and OpenShift Pipelines.
 
 == Jenkins terminology
 Jenkins offers declarative and scripted pipelines that are extensible using shared libraries and plugins. Some basic terms in Jenkins are as follows:
 
-* *Pipeline*: Automates the entire process of building, testing, and deploying applications, using the link:https://groovy-lang.org/[Groovy] syntax.
+* *Pipeline*: Automates the entire process of building, testing, and deploying applications by using link:https://groovy-lang.org/[Groovy] syntax.
 * *Node*: A machine capable of either orchestrating or executing a scripted pipeline.
-* *Stage*: A conceptually distinct subset of tasks performed in a pipeline. Plugins or user interfaces often use this block to display status or progress of tasks.
+* *Stage*: A conceptually distinct subset of tasks performed in a pipeline. Plugins or user interfaces often use this block to display the status or progress of tasks.
 * **Step**: A single task that specifies the exact action to be taken, either by using a command or a script.
 
-== Tekton terminology
-Tekton uses the link:https://yaml.org/[YAML] syntax for declarative pipelines and consists of tasks. Some basic terms in Tekton are as follows:
+== OpenShift Pipelines terminology
+OpenShift Pipelines uses link:https://yaml.org/[YAML] syntax for declarative pipelines and consists of tasks. Some basic terms in OpenShift Pipelines are as follows:
 
 * **Pipeline**: A set of tasks in a series, in parallel, or both.
 * **Task**: A sequence of steps as commands, binaries, or scripts.
@@ -27,7 +28,7 @@ Tekton uses the link:https://yaml.org/[YAML] syntax for declarative pipelines an
 ====
 You can initiate a PipelineRun or a TaskRun with a set of inputs such as parameters and workspaces, and the execution results in a set of outputs and artifacts.
 ====
-* **Workspace**: In Tekton, workspaces are conceptual blocks that serve the following purposes:
+* **Workspace**: In OpenShift Pipelines, workspaces are conceptual blocks that serve the following purposes:
 
 ** Storage of inputs, outputs, and build artifacts.
 
@@ -38,16 +39,16 @@ You can initiate a PipelineRun or a TaskRun with a set of inputs such as paramet
 +
 [NOTE]
 ====
-In Jenkins, there is no direct equivalent of Tekton workspaces. You can think of the control node as a workspace, as it stores the cloned code repository, build history, and artifacts. In situations where a job is assigned to a different node, the cloned code and the generated artifacts are stored in that node, but the build history is maintained by the control node.
+In Jenkins, there is no direct equivalent of OpenShift Pipelines workspaces. You can think of the control node as a workspace, as it stores the cloned code repository, build history, and artifacts. When a job is assigned to a different node, the cloned code and the generated artifacts are stored in that node, but the control node maintains the build history.
 ====
 
 == Mapping of concepts
-The building blocks of Jenkins and Tekton are not equivalent, and a comparison does not provide a technically accurate mapping. The following terms and concepts in Jenkins and Tekton correlate in general:
+The building blocks of Jenkins and OpenShift Pipelines are not equivalent, and a specific comparison does not provide a technically accurate mapping. The following terms and concepts in Jenkins and OpenShift Pipelines correlate in general:
 
-.Jenkins and Tekton - basic comparison
+.Jenkins and OpenShift Pipelines - basic comparison
 [cols="1,1",options="header"]
 |===
-|Jenkins|Tekton
+|Jenkins|OpenShift Pipelines
 |Pipeline|Pipeline and PipelineRun
 |Stage|Task
 |Step|A step in a task

cicd/jenkins-tekton/images cicd/jenkins/imagescicd/jenkins-tekton/images renamed to cicd/jenkins/images

@@ -0,0 +1,18 @@
+// Module included in the following assembly:
+//
+// jenkins/migrating-from-jenkins-to-openshift-pipelines.adoc
+
+:_content-type: CONCEPT
+[id="jt-comparison-of-jenkins-openshift-pipelines-execution-models_{context}"]
+= Comparison of Jenkins and OpenShift Pipelines execution models
+
+Jenkins and OpenShift Pipelines offer similar functions but are different in architecture and execution.
+
+.Comparison of execution models in Jenkins and OpenShift Pipelines
+[cols="1,1",options="header"]
+|===
+|Jenkins|OpenShift Pipelines
+|Jenkins has a controller node. Jenkins runs pipelines and steps centrally, or orchestrates jobs running in other nodes.|OpenShift Pipelines is serverless and distributed, and there is no central dependency for execution.
+|Containers are launched by the Jenkins controller node through the pipeline.|OpenShift Pipelines adopts a 'container-first' approach, where every step runs as a container in a pod (equivalent to nodes in Jenkins).
+|Extensibility is achieved by using plugins.|Extensibility is achieved by using tasks in Tekton Hub or by creating custom tasks and scripts.
+|===