From d09d938eeb8e878eb2b2425a4390718347a52ccd Mon Sep 17 00:00:00 2001 From: Alex Kochnev Date: Wed, 20 Mar 2019 12:13:59 -0400 Subject: [PATCH] Minor typo fix --- devops-pipeline-scm.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devops-pipeline-scm.adoc b/devops-pipeline-scm.adoc index 6d1e72b..8d9155d 100644 --- a/devops-pipeline-scm.adoc +++ b/devops-pipeline-scm.adoc @@ -7,7 +7,7 @@ Although it is convenient to embed a Jenkinsfile into an OpenShift Pipeline and Using OpenShift Pipeline, you can store Jenkinsfiles in a Git repository and reference it in the JenkinsPipeline buildconfig. Whenever the pipeline starts running, OpenShift fetches the latest version the references Jenkinsfile from the Git repository and adjusts the pipeline steps accordingly. In this lab you will create an OpenShift Pipeline with the Jenkinsfile stored in a Git repository. -Although CI/CD is a fairly new in many organizations, teams have been building Continuous Integration flows for a long time and have invested lots of time improving and refining that process. For Java projects, the CI flow generally moves around building the application JAR/WAR/EAR, running the unit-tests suits and integration tests and if successful, releasing the application binaries into a repository manager like Sonatype Nexus and Artifactory. In this lab, you will modify the pipeline in order to extend existing CI processes and build upon the Maven build and test flow that exists in many development teams. +Although CI/CD is a fairly new in many organizations, teams have been building Continuous Integration flows for a long time and have invested lots of time improving and refining that process. For Java projects, the CI flow generally moves around building the application JAR/WAR/EAR, running the unit-tests suites and integration tests and if successful, releasing the application binaries into a repository manager like Sonatype Nexus and Artifactory. In this lab, you will modify the pipeline in order to extend existing CI processes and build upon the Maven build and test flow that exists in many development teams. The following diagram shows the pipeline stages. For the sake simplicity, pushing the artifacts to an artifact repository is not included in this pipeline however you can include that using the https://jenkins.io/doc/pipeline/steps/nexus-artifact-uploader/[Nexus Artifact Uploader Plugin] for Sonatype Nexus and https://jenkins.io/doc/pipeline/steps/artifactory/#artifactoryupload-upload-artifacts[Artifactory Plugin] for Artifactory.