Skip to content

Fix minor typos and grammatical errors #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: ocp-3.11
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _modules.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,4 @@ modules:
devops-custom-slave:
name: Creating Custom Jenkins Slave Pods
devops-env-info:
name: "Appnedix: Lab Environment"
name: "Appendix: Lab Environment"
2 changes: 1 addition & 1 deletion devops-deployment-envs.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ By default, the current user who created the project is the _admin_ for this pro

image::devops-envs-dev-membership.png[Project Access Control, width=800]

Now, let’s deploy the Spring Boot application, Cart service, into the Dev environment. OpenShift supports deploying containerized apps in three different ways and allows developer to pick the process that is most suitable for their projects:
Now, let’s deploy the Spring Boot application, Cart service, into the Dev environment. OpenShift supports deploying containerized apps in three different ways and allows developers to pick the process that is most suitable for their projects:

* From application source code
* From application binary (e.g. app.jar)
Expand Down
2 changes: 1 addition & 1 deletion devops-pipeline-scm.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Using OpenShift Pipeline, you can store Jenkinsfiles in a Git repository and ref

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.

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.
The following diagram shows the pipeline stages. For the sake of 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.

image::devops-pipeline-scm-diagram.png[Pipeline Diagram]

Expand Down