저장소 권한 Updater

제품정보

Jenkins 프로젝트는 Artifactory의 핵심 및 플러그인 릴리스와 같은 Maven artifacts를 호스팅합니다.

이 권한 시스템은 GitHub의 독립적이며, 사용자 (Jenkins LDAP 계정과 같은 wiki 및 JIRA)가 artifacts에 업로드 할 수 있습니다.

이 저장소에는 YAML 형식의 Artifactory 업로드 허가에 대한 정의뿐만 아니라 Artifactory에 동기화하는 도구가 포함되어 있습니다.

주의: 이 권한은 uploading artifacts 에 Jenkins 프로젝트의 Maven 저장소. GitHub 저장소 권한의 독립적입니다. 당신은 다른없이 하나가있을 수 있습니다. 일반적으로 GitHub 저장소에 두 가지가 있습니다.

자주 묻는 질문

jenkinsci]에서 새로운 플러그인을 호스트하려면 GitHub 조직은 호스팅 요청을 엽니다. 더 많은 정보를 호스팅하는 문서 보기.

Jenkins Hosting Checker는 모든 호스팅 요청에 대한 의견이 발견되고 호스팅 팀은 요청을 한 번 조정합니다.

Repository Permissions Updater

About

The Jenkins project hosts Maven artifacts such as core and plugin releases on Artifactory.

Its permissions system is independent of GitHub’s, and we limit which users (identified by the Jenkins LDAP account, same as wiki and JIRA) are allowed to upload which artifacts.

This repository contains both the definitions for Artifactory upload permissions in YAML format, as well as the tool that synchronizes them to Artifactory.

Note: These permissions are specifically for uploading artifacts to the Jenkins project’s Maven repository. It is independent of GitHub repository permissions. You may have one without the other. Typically, you’ll either have both, or just the GitHub repository access.

Requesting Hosting

To host a new plugin in the jenkinsci GitHub organization, open a hosting request. See the hosting documentation for more information.

The Jenkins Hosting Checker comments on every hosting request with the problems it finds, and the hosting team reviews the request once those are fixed. Please run the same checks yourself before opening the request so it can be processed without rounds of fixing and re-checking.

Running the hosting checks locally

Requirements: Java 25 or newer, Maven, and a GitHub token (no scopes needed). If you have the GitHub CLI logged in, its token is picked up automatically; otherwise set GITHUB_OAUTH (or GITHUB_TOKEN).

The checks read your repository from GitHub, so push your changes first, then:

git clone https://github.com/jenkins-infra/repository-permissions-updater.git
cd repository-permissions-updater
./bin/check-hosting.sh \
  --repository-url https://github.com/your-org/your-cool-plugin \
  --new-repository-name your-cool-plugin \
  --github-user your-github-user \
  --jenkins-user your-jenkins-account

• --repository-url: the repository to host, as you will enter it in the hosting request.
• --new-repository-name: the name it will have in jenkinsci, -plugin. Defaults to the current repository name.
• --github-user: GitHub users to have commit permission, comma separated or repeated.
• --jenkins-user: Jenkins community accounts to have release permission, comma separated or repeated.
• --no-cd: add this if you will not request automated releases via GitHub Actions.

The first run builds the checker. After pulling updates to this repository, run with REBUILD=1 to use the latest checks. Set VERBOSE=1 to see the checker’s full log. The script exits with 0 when no issues marked Required are found, and 1 when there are issues to fix.