You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some specific (multibranch) projects, using declarative pipeline Jenkinsfile, for which I'd like to skip the status update.
Rationale: I'm building some GitHub projects for which the Jenkins/Gihub user has no write rights, and I'd prefer NOT to have the error message:
Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected,
or the next message
GitHub has been notified of this commit’s build result (which, by the way, is incorrect in my case because of the previous error).
Any way to override the global configuration in a declarative (or scripted) pipeline, and to disable this on a per-project basis ?
Thanks !
The text was updated successfully, but these errors were encountered:
I'm also curious about this feature. This would allow us to be more specific on a per-project bases. In some repositories we have many stages but it's not necessary to see the status of each individual one on GitHub. Right now it just clutters the checks view on GitHub.
Hello,
I have some specific (multibranch) projects, using declarative pipeline Jenkinsfile, for which I'd like to skip the status update.
Rationale: I'm building some GitHub projects for which the Jenkins/Gihub user has no write rights, and I'd prefer NOT to have the error message:
Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected
,or the next message
GitHub has been notified of this commit’s build result
(which, by the way, is incorrect in my case because of the previous error).Any way to override the global configuration in a declarative (or scripted) pipeline, and to disable this on a per-project basis ?
Thanks !
The text was updated successfully, but these errors were encountered: