Skip to content

Fix required role level for Jenkins-to-GitHub built status notifications

Tarmo Kuuserequested to merge
tarmo-powerup/gitlab:tarmo-powerup-master-patch-77531 into master

What does this MR do and why?

Documentation states that CI use must have role "Developer" in project. Unfortunately this does not suffice build status notifications (returns HTTP 403 when calling updateGitlabCommitStatus in Jenkinsfile). Correct role is "Maintainer" as specified in https://github.com/jenkinsci/gitlab-plugin#jenkins-to-gitlab-authentication

Screenshots or screen recordings

If using "Developer" role:

[Pipeline] updateGitlabCommitStatus
Failed to update Gitlab commit status for project 'powerup-technologies/others/jenkins_example': HTTP 403 Forbidden

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports