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

mention required permissions for commit status API 

Since gitlab 8.5 the reporter permissions are no longer sufficient to post commit statuses.
055afab5c7 (2d52ce552f2d21beb86ec07b784cb47791f894cc_161_172)
This commit is contained in:
Martin Nowak 2016-03-15 02:46:59 +01:00
parent 5d63029e6d
commit 42611a7c1c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -85,7 +85,7 @@ If you plan to use forked repositories, you will need to enable the GitLab CI in
### GitLab Configuration (>= 8.1) ### GitLab Configuration (>= 8.1)
GitLab 8.1 uses the same configuration as GitLab 8.0 GitLab 8.1 uses the same configuration as GitLab 8.0
* GitLab 8.1 has implemented a commit status api. To enable this check the ``Use GitLab CI features`` under the project settings. * GitLab 8.1 has implemented a commit status api. To enable this check the ``Use GitLab CI features`` under the project settings.
* Configure access to GitLab as described above in "Configure access to GitLab" * Configure access to GitLab as described above in "Configure access to GitLab" (the account needs at least developer permissions to post commit statuses)
### Forked repositories ### Forked repositories
If you plan to use forked repositories, you will need to enable the GitLab CI integration on **each fork**. If you plan to use forked repositories, you will need to enable the GitLab CI integration on **each fork**.