Репозиторий Permissions Updater

О нас

Проект Jenkins содержит артефакты Maven, такие как релизы ядра и плагинов на Artifactory.

Его система разрешений не зависит от GitHub, и мы ограничиваем, какие пользователи (идентифицируемые учетной записью Jenkins LDAP, такой же как вики и JIRA) могут загружать какие артефакты.

Это хранилище содержит как определения для разрешений на загрузку Artifactory в формате YAML, так и инструмент, который синхронизирует их с Artifactory.

Примечание: Эти разрешения предназначены специально для загрузки артефактов в репозиторий Maven проекта Jenkins. Он не зависит от разрешений репозитория 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.