jenkinsci / jenkinsci/git-plugin
[JENKINS-70735] Make git notifyCommit apiTokens configurable via JCasC
- Dominant language
- Java
- Stars
- 694
- Forks
- 1.1k
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 3
Description
The GIT plugin by default requires a token for calling notifyCommit since plugin version 4.11.4.
As there is no way to provide apiTokens via JCasC one has to either
- disable the token requirement by setting the system property hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL to either disabled-for-polling or disabled
- manually create a token via "Configure Global Security"
This prevents instances from being fully automatically provisioned via JCasC without sacrificing an additional level of security.
It would be great if a list of apiTokens could be provided via JCasC.
---
Originally reported by kjauch, imported from: Make git notifyCommit apiTokens configurable via JCasC
Raw content of original issue
The GIT plugin by default requires a token for calling notifyCommit since plugin version 4.11.4.
As there is no way to provide apiTokens via JCasC one has to either
- disable the token requirement by setting the system property hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL to either disabled-for-polling or disabled
- manually create a token via "Configure Global Security"
This prevents instances from being fully automatically provisioned via JCasC without sacrificing an additional level of security.
It would be great if a list of apiTokens could be provided via JCasC.
Contributor guide
Assessment
This issue has not been assessed yet.