Use CI_JOB_TOKEN for access in Gitlab using new token access feature in 15.9 #20336
roemba
started this conversation in
Suggest an Idea
Replies: 1 comment 12 replies
|
I'm not sure what you mean specifically. Renovate doesn't force which type of token you use today. |
12 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Type of discussion.
I'm proposing an idea
Tell us more.
The Renovate documentation mentions a Gitlab issue that has now been closed and the feature it mentions is deployed in 15.9
It seems a relatively small change to make in Renovate where it will use the CI_JOB_TOKEN for API access if so configured. The CI_JOB_TOKEN for the project it is running in can then be used to access other projects by configuring some settings in Gitlab. See https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#add-a-project-to-the-inbound-job-token-scope-allowlist
This will allow running Renovate in Gitlab without creating a user for it which can be very useful if a user pays a license with limited seats.
All reactions