Skip to content

Commit 4c31398

Browse files
author
Jamie Strusz
authored
Fix title caps
1 parent bbc1c43 commit 4c31398

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

hooks/jenkins/master-branch-protect/branch-protect.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,20 @@
44
- [Upgrading Jenkins in Docker](#upgrading-jenkins-in-docker)
55
* [Installing Jenkins on RedHat/CentOS 7](#installing-jenkins-on-redhatcentos-7)
66
* [Installing Jenkins on Ubuntu/Debian](#installing-jenkins-on-ubuntudebian)
7-
* [Additional Installation Options](#additional-installation-options)
8-
* [Obtaining the Initial Password](#obtaining-the-initial-password)
7+
* [Additional installation options](#additional-installation-options)
8+
* [Obtaining the initial password](#obtaining-the-initial-password)
99
- [Docker](#docker)
1010
- [Linux](#linux)
11-
* [Completing the Setup](#completing-the-setup)
12-
- [Installing Plugins](#installing-plugins)
11+
* [Completing the setup](#completing-the-setup)
12+
- [Installing plugins](#installing-plugins)
1313
- [Styling Jenkins](#styling-jenkins)
14-
- [Creating the Webhook](#creating-the-webhook)
15-
- [Creating the Pipeline](#creating-the-pipeline)
16-
* [Git Credentials in Jenkins](#git-credentials-in-jenkins)
17-
* [Defining Our Actions](#defining-our-actions)
18-
* [Defining the Payload](#defining-the-payload)
19-
* [Tying it all Together](#tying-it-all-together)
20-
- [Adding the Pipeline to Jenkins as a Webhook Listener](#adding-the-pipeline-to-jenkins-as-a-webhook-listener)
14+
- [Creating the webhook](#creating-the-webhook)
15+
- [Creating the pipeline](#creating-the-pipeline)
16+
* [Git credentials in Jenkins](#git-credentials-in-jenkins)
17+
* [Defining our actions](#defining-our-actions)
18+
* [Defining the payload](#defining-the-payload)
19+
* [Tying it all together](#tying-it-all-together)
20+
- [Adding the pipeline to Jenkins as a webhook listener](#adding-the-pipeline-to-jenkins-as-a-webhook-listener)
2121

2222
# Overview
2323
The purpose of this guide is to address a particular scenario, wherein repositories are created but no branches are protected. In this example we will utilize `Jenkins` to process _webhooks_ that GitHub sends each time a branch is created. Once the webhook is received, Jenkins will analyse the payload and make an API call back to GitHub to:
@@ -516,7 +516,7 @@ Build Token | [_uuid_ from Creating the Webhook](#creating-the-webhook)
516516

517517
![create jenkins pipeline](https://user-images.githubusercontent.com/865381/39252653-1c318d56-4874-11e8-90d6-2ba21b5fa20f.gif)
518518

519-
## Triggering the Build
519+
## Triggering the build
520520
Once you have the pipeline created, simply create a new repository and initialize it with some content. The creation of that first branch will trigger the webhook and execute the pipeline.
521521

522522
1. Login to GitHub
@@ -525,7 +525,7 @@ Once you have the pipeline created, simply create a new repository and initializ
525525

526526
![create repository](https://user-images.githubusercontent.com/865381/39252675-2c087d84-4874-11e8-9fc7-3bf6d950caf0.gif)
527527

528-
## The Completed Workflow
528+
## The completed workflow
529529
Once the pipeline has been triggered and completes, view the console output to see the payload and actions taken.
530530

531531
<details>

0 commit comments

Comments
 (0)