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

Update README.md

This commit is contained in:
Anthony Mastrean 2017-09-20 14:22:49 -04:00 committed by GitHub
parent 9a59c37305
commit 46bcdf8349
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -95,7 +95,7 @@ checkout changelog: true, poll: true, scm: [
```
### Git configuration for Multibranch Pipeline/Workflow jobs
**Note:** none of the GitLab environment variables are available for mulitbranch pipeline jobs as there is no way to pass some additional data to a multibranch pipeline build while notifying a multibranch pipeline job about SCM changes.
**Note:** none of the GitLab environment variables are available for multibranch pipeline jobs as there is no way to pass some additional data to a multibranch pipeline build while notifying a multibranch pipeline job about SCM changes.
Due to this the plugin just listens for GitLab Push Hooks for multibranch pipeline jobs; Merge Request hooks are ignored.
1. Click **Add source**
@ -222,7 +222,7 @@ To use GitLab with Flexible Publish, configure the *Post-build Actions* as follo
## Gitlab Configuration
GitLab 8.1 has implemented a commit status api, you need an extra post-build step to support commit status.
GitLab 8.1 has implemented a commit status API, you need an extra post-build step to support commit status.
* In GitLab go to your repository's project *Settings*
* Click on *Web Hooks*
@ -365,4 +365,4 @@ See https://github.com/jenkinsci/gitlab-plugin/tree/master/src/docker/README.md
# Release Workflow
To perform a full plugin release, maintainers can run ``mvn release:prepare release:perform`` To release a snapshot, e.g. with a bug fix for users to test, just run ``mvn deploy``
To perform a full plugin release, maintainers can run ``mvn release:prepare release:perform`` To release a snapshot, e.g. with a bug fix for users to test, just run ``mvn deploy``