> > On 20. Sep 2017, at 22:31, James Nord <[email protected]> wrote: > > In order to demonstrate the changes in Jenkins I would like to be able to > push a snapshot of stapler to our repo so the PR can consume it. >
Any registered user can deploy any snapshot. (This was changed shortly after introduction of per-artifact permissions as it wasn't really necessary to ensure no unauthorized bits get distributed, and it makes multi-repo PRs easier.) > I would also like to be able to push a custom version (0) or the old > servlet-api ( javax.servlet:servlet-api:0) to prevent any plugins from > getting a version of it when using a new core. > > (and at the same time a version zero of commons-logging for the same reason) > > Is this possible - seems like its not a HOSTING request nor an INFRA request > so not sure what route to go down to ask for this... File a PR to https://github.com/jenkins-infra/repository-permissions-updater/ (prefix probably "component" instead of "plugin") and explain it in the PR description. Similar recently changed files were for example https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/component-docker-java-shaded.yml or https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/component-trilead-ssh2.yml -- while unusual it's not unprecedented. Is this something better resolved by JENKINS-30685 and/or JENKINS-28942? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1D58B4F4-85E9-4F6C-8F66-16EE1C6B6F8C%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
