abdullah/cje-prep
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Capitalize words in titles

Browse Source
This commit is contained in:
Benjamin Muschko
2019-07-28 11:27:26 +02:00
parent 3b51cbc782
commit f809a2d80a
11 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
04-scm-configuration.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Configuring a GitHub repository ## Configuring a GitHub Repository
1. Create a new freestyle job named `gradle-initializr`. 1. Create a new freestyle job named `gradle-initializr`.
2. Configure Git as the SCM and use the repository URL `git@github.com:bmuschko/gradle-initializr.git`. Only build from the branch `master`. 2. Configure Git as the SCM and use the repository URL `git@github.com:bmuschko/gradle-initializr.git`. Only build from the branch `master`.

2
05-test-execution-and-reporting.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Displaying JUnit and JaCoCo test results ## Displaying JUnit and JaCoCo Test Results
1. Configure the `gradle-initializr` project to parse the JUnit XML results for unit test. The files can be found in the directory `build/test-results/test`. 1. Configure the `gradle-initializr` project to parse the JUnit XML results for unit test. The files can be found in the directory `build/test-results/test`.
2. Execute the build twice to generate a graph. Have a look at the executed tests in the test results. 2. Execute the build twice to generate a graph. Have a look at the executed tests in the test results.

2
06-notifications.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Notifying the team upon a broken build ## Notifying the Team Upon a Broken Build
1. Change the list of Gradle tasks to `doesnotexist` to emulate a failure. The build will fail as the task doesn't exist in the build script. 1. Change the list of Gradle tasks to `doesnotexist` to emulate a failure. The build will fail as the task doesn't exist in the build script.
2. Install the Google Chat plugin. 2. Install the Google Chat plugin.

2
07-artifacts.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Storing and fingerprinting artifacts ## Storing and Fingerprinting Artifacts
1. Create a post-build action for archiving JAR file with the pattern `build/libs/*.jar`. 1. Create a post-build action for archiving JAR file with the pattern `build/libs/*.jar`.
2. Execute the build. The build should list the artifact `gradle-initializr-1.0.0.jar`. 2. Execute the build. The build should list the artifact `gradle-initializr-1.0.0.jar`.

2
08-matrix-security.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Creating a user and setting permissions ## Creating a User and Setting Permissions
1. Ensure that you are logged in as admin user. 1. Ensure that you are logged in as admin user.
2. Create a new user named `miller`. Provide the relevant information. 2. Create a new user named `miller`. Provide the relevant information.

2
09-rest-api.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Using the REST API for common operations ## Using the REST API for Common Operations
1. Create a new user named `buildbot`. 1. Create a new user named `buildbot`.
2. Add adminstration permissions for the user. 2. Add adminstration permissions for the user.

2
10-distributed-builds.md
View File

@@ -1,6 +1,6 @@
# Key CI/CD/Jenkins Concepts and their Usage # Key CI/CD/Jenkins Concepts and their Usage
## Configuring and executing jobs in a distributed build ## Configuring and Executing Jobs in a Distributed Build
1. Go to "Manage Jenkins" > "Manage Nodes". You should see a single `master` node. 1. Go to "Manage Jenkins" > "Manage Nodes". You should see a single `master` node.
2. Configure the `master` node by setting the # of executor value to 0. That will take care of never using the `master` for job workload. 2. Configure the `master` node by setting the # of executor value to 0. That will take care of never using the `master` for job workload.

2
11-pipeline-job.md
View File

@@ -1,6 +1,6 @@
# Building Continuous Delivery (CD) Pipelines # Building Continuous Delivery (CD) Pipelines
## Creating a pipeline job ## Creating a Pipeline Job
1. Have a look at the [repository](https://github.com/bmuschko/todo-spring-boot) `bmuschko/todo-spring-boot` on GitHub. The repository already contains the build definition in the form of a `Jenkinsfile`. Identify each of the steps. 1. Have a look at the [repository](https://github.com/bmuschko/todo-spring-boot) `bmuschko/todo-spring-boot` on GitHub. The repository already contains the build definition in the form of a `Jenkinsfile`. Identify each of the steps.
2. In Jenkins, set up the credentials `SONARCLOUD_TOKEN` and `HEROKU_API_KEY` if they don't exist yet. 2. In Jenkins, set up the credentials `SONARCLOUD_TOKEN` and `HEROKU_API_KEY` if they don't exist yet.

2
12-basic-jenkinsfile.md
View File

@@ -1,6 +1,6 @@
# Building Continuous Delivery (CD) Pipelines # Building Continuous Delivery (CD) Pipelines
## Writing a basic Jenkinsfile ## Writing a Basic Jenkinsfile
1. Create a new GitHub repository named `go-on-jenkins`. 1. Create a new GitHub repository named `go-on-jenkins`.
2. Create a new `Jenkinsfile` in the root directory of the repository as well as a simple `main.go` file. The main function just prints "Hello World!". Initialize the project via Go Modules. 2. Create a new `Jenkinsfile` in the root directory of the repository as well as a simple `main.go` file. The main function just prints "Hello World!". Initialize the project via Go Modules.

2
13-advanced-jenkinsfile.md
View File

@@ -1,6 +1,6 @@
# Building Continuous Delivery (CD) Pipelines # Building Continuous Delivery (CD) Pipelines
## Enhancing a pipeline with advanced features ## Enhancing a Pipeline With Advanced Features
We'll want to enhance the pipeline by additional stages and implement a release workflow. The project is going to use an external tool called GoReleaser to publish cross-compiled artifacts to GitHub Releases. The binaries should only be released if the commit has been tagged. We'll want to enhance the pipeline by additional stages and implement a release workflow. The project is going to use an external tool called GoReleaser to publish cross-compiled artifacts to GitHub Releases. The binaries should only be released if the commit has been tagged.

2
14-shared-library.md
View File

@@ -1,6 +1,6 @@
# Building Continuous Delivery (CD) Pipelines # Building Continuous Delivery (CD) Pipelines
## Writing and using a shared library ## Writing and Using a Shared Library
1. Set up a new GitHub repository named `jenkins-standard-go-pipeline`. It will define a standard pipeline definition for Go projects implemented as shared library. 1. Set up a new GitHub repository named `jenkins-standard-go-pipeline`. It will define a standard pipeline definition for Go projects implemented as shared library.
2. Add the file `vars/standard.groovy` that defines the declarative pipeline as global variable. Make the Go tool name and golang-ci version configurable with the help of parameters. 2. Add the file `vars/standard.groovy` that defines the declarative pipeline as global variable. Make the Go tool name and golang-ci version configurable with the help of parameters.