Skip to content

Commit cc76563

Browse files
author
Jamie Strusz
authored
Fix Jira caps
1 parent 5e1a813 commit cc76563

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

hooks/jenkins/jira-issue-validator/jira-issue-validator.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Jira Issue Validator
1+
## Jira issue validator
22
In order to use this pipeline, you will need the following plugins:
33

44
- [Pipeline](https://plugins.jenkins.io/workflow-aggregator): This plugin allows us to store our `Jenkins` _jobs_ as code, and moves away from the common understanding of Jenkins `builds` to an `Agile` and `DevOps` model
@@ -9,14 +9,14 @@ In order to use this pipeline, you will need the following plugins:
99
- [GitHub Integration](https://plugins.jenkins.io/github-pullrequest): Provides the ability to customize pull request builds
1010
- [Pipeline: GitHub](https://plugins.jenkins.io/pipeline-github): Allows using GitHub steps within a _Jenkinsfile_
1111
- [GitHub](https://plugins.jenkins.io/github): Provides integration with GitHub
12-
- [JIRA Pipeline Steps](https://plugins.jenkins.io/jira-steps): Allows using JIRA steps within a _Jenkinsfile_
13-
- [JIRA](https://plugins.jenkins.io/jira): Enables integration with JIRA
12+
- [Jira Pipeline Steps](https://plugins.jenkins.io/jira-steps): Allows using Jira steps within a _Jenkinsfile_
13+
- [Jira](https://plugins.jenkins.io/jira): Enables integration with Jira
1414

1515
### Configuring Jenkins
1616

1717
1. Log in to Jenkins and click _Manage Jenkins_
1818
2. Click _Configure System_
19-
3. In the **JIRA Steps** section, provide the required information for connecting to your JIRA server
19+
3. In the **Jira Steps** section, provide the required information for connecting to your Jira server
2020
![jenkins-setup-jira](https://user-images.githubusercontent.com/865381/39254110-587316e2-4877-11e8-93f0-9050a7144ea2.png)
2121
4. In the **GitHub Pull Request Builder** section, fill out the connection information
2222
![jenkins-config-gh-pull-1](https://user-images.githubusercontent.com/865381/39254113-5d8fde58-4877-11e8-81f5-fb037ae06266.png)
@@ -36,7 +36,7 @@ In order to use this pipeline, you will need the following plugins:
3636

3737

3838
### Example Pipeline
39-
This pipeline functions by taking the _issue ID_ from the pull request body, performing a lookup in JIRA, then setting the status of the build in GitHub based on the _transition_ in JIRA.
39+
This pipeline functions by taking the _issue ID_ from the pull request body, performing a lookup in Jira, then setting the status of the build in GitHub based on the _transition_ in Jira.
4040

4141
```groovy
4242
node {
@@ -95,7 +95,7 @@ node {
9595
```
9696

9797
### Visual Status
98-
1. Create a new file with a commit message. The JIRA plugin will automatically comment on the ticket if you use the `JIRA-[number] #comment <comment>` format
98+
1. Create a new file with a commit message. The Jira plugin will automatically comment on the ticket if you use the `JIRA-[number] #comment <comment>` format
9999
![jenkins-jira-commit](https://user-images.githubusercontent.com/865381/37779241-544b8bc8-2dc2-11e8-8dd6-aaca12556ed0.png)
100100

101101
2. Create a new pull request, and be sure that `JIRA-[number]` is the first word in the _body_

0 commit comments

Comments
 (0)