Open Dohbedoh opened 2 years ago
The wildcard in the permissions file doesn't actually work, because the file names are (dis)allowed based on the name
. See this repo's readme.
It works for https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-aws-java-sdk.yml because the name
is a true prefix of all file names (we cannot only allow name-version
, so it's name-*
). It doesn't work here because name
includes -api
.
Just don't use this trick. Nobody understands how this actually works, and it creates tons of problems.
I see. Thanks for the explanation, will propose a fix then.
Reproduction steps
The automated CD release of a new plugin jenkinsci/mina-sshd-api-plugin fails to deploy the module plugins in nexus. Note that the plugin is a multi module plugin (like the aws java sdk plugin for example)
Expected Results
The CD release should deploy the following:
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/mina-sshd-api/mina-sshd-api-parent/
(parent pom)https://repo.jenkins-ci.org/releases/io/jenkins/plugins/mina-sshd-api/mina-sshd-common-api/
(hpi)https://repo.jenkins-ci.org/releases/io/jenkins/plugins/mina-sshd-api/mina-sshd-core-api/
(hpi)https://repo.jenkins-ci.org/releases/io/jenkins/plugins/mina-sshd-api/mina-sshd-sftp-api/
(hpi)https://repo.jenkins-ci.org/releases/io/jenkins/plugins/mina-sshd-api/mina-sshd-ssh-api/
(hpi)Actual Results
The CD release fails to deploy the modules:
Anything else?
The plugin was hosted recently and haven't been released yet:
There is some discussion about the repository paths in:
cc @jglick