p85947160
/
Gitee-Jenkins-Plugin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix spelling mistakes

This commit is contained in:
Owen Mehegan 2018-01-15 18:28:58 +11:00
parent e7bcb9e6b4
commit a7938df166
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -294,13 +294,13 @@ In order to build when a new tag is pushed:
* In the ``GitLab server`` add ``Tag push events`` to the ``Web Hook`` * In the ``GitLab server`` add ``Tag push events`` to the ``Web Hook``
* In the ``Jenkins`` under the ``Source Code Management`` section: * In the ``Jenkins`` under the ``Source Code Management`` section:
* select ``Advance...`` and add ``+refs/tags/*:refs/remotes/origin/tags/*`` as ``Refspec`` * select ``Advance...`` and add ``+refs/tags/*:refs/remotes/origin/tags/*`` as ``Refspec``
* you can also use ``Branch Specifier`` to specify which tag need to be built (exampple ``refs/tags/${TAGNAME}``) * you can also use ``Branch Specifier`` to specify which tag need to be built (example ``refs/tags/${TAGNAME}``)
# Send message on complete of a build # Send message on complete of a build
1. In the *Post build steps* section: 1. In the *Post build steps* section:
1. Click *Add post build step* 1. Click *Add post build step*
2. Click *Add note with build status on GitLab merge requests* and save build settings (You enabled autoumatically sending default message on result of a build) 2. Click *Add note with build status on GitLab merge requests* and save build settings (You enabled automatically sending default message on result of a build)
2. If you want make custom message on result of a build: 2. If you want make custom message on result of a build:
1. In *Add note with build status on GitLab merge requests* section click to *Custom message on success/failure/abort* 1. In *Add note with build status on GitLab merge requests* section click to *Custom message on success/failure/abort*

2
src/docker/README.md
View File

@ -4,7 +4,7 @@ In order to test the plugin on different versions of `GitLab` and `Jenkins` you
A example docker-compose file is available at `gitlab-plugin/src/docker` which allows to set up instances of the latest `GitLab` and `Jenkins` versions. A example docker-compose file is available at `gitlab-plugin/src/docker` which allows to set up instances of the latest `GitLab` and `Jenkins` versions.
If they don't already exist, create the following directories and make sure the user that Docker is runnning as owns them: If they don't already exist, create the following directories and make sure the user that Docker is running as owns them:
* /srv/docker/gitlab/postgresql * /srv/docker/gitlab/postgresql
* /srv/docker/gitlab/gitlab * /srv/docker/gitlab/gitlab
* /srv/docker/gitlab/redis * /srv/docker/gitlab/redis

4
src/test/java/com/dabsquared/gitlabjenkins/publisher/GitLabCommitStatusPublisherTest.java
View File

@ -420,11 +420,11 @@ public class GitLabCommitStatusPublisherTest {
return build; return build;
} }
private String getSingleProjectJson(String name,String projectNameWithNamespace, int porjectId) throws IOException { private String getSingleProjectJson(String name,String projectNameWithNamespace, int projectId) throws IOException {
String nameSpace = projectNameWithNamespace.split("/")[0]; String nameSpace = projectNameWithNamespace.split("/")[0];
String projectName = projectNameWithNamespace.split("/")[1]; String projectName = projectNameWithNamespace.split("/")[1];
return IOUtils.toString(getClass().getResourceAsStream(name)) return IOUtils.toString(getClass().getResourceAsStream(name))
.replace("${projectId}", porjectId + "") .replace("${projectId}", projectId + "")
.replace("${nameSpace}", nameSpace) .replace("${nameSpace}", nameSpace)
.replace("${projectName}", projectName); .replace("${projectName}", projectName);
} }