[Jenkins-infra] Fine-grained Artifactory upload permissions

Michael Neale mneale at cloudbees.com
Mon Aug 22 09:42:19 UTC 2016


A PR for this - is this kind of right? 
https://github.com/jenkins-infra/repository-permissions-updater/pull/2



On Saturday, August 20, 2016 at 10:18:33 PM UTC+10, Daniel Beck wrote:
>
> Hi everyone, 
>
> I just enabled fine-grained Artifactory upload permissions, limiting who 
> is allowed to upload which artifacts. 
>
> What does this mean for you as Jenkins plugin developers? 
>
> Ideally, nothing more than a quick PR to this repository before you 
> release any particular plugin or other component _for the first time_: 
>
> https://github.com/jenkins-infra/repository-permissions-updater/ 
>
> I initialized permissions based on uploads since January 2014, so if 
> you've uploaded a plugin or other artifact since then, you should be in the 
> list of authorized uploaders (data you can check is in that repo). As this 
> wasn't a fully automated process, and there's a number of special 
> snowflakes in the repository, it's possible I accidentally left you out. In 
> that case, please file a PR as described in that repository's README, and 
> we'll get you set up. 
>
> A few notes: 
>
> - I'm still working through recent hosting requests. If your plugin is 
> unreleased, there is no corresponding permissions file, so uploads may 
> fail. 
> - Documentation beyond this email and the repository README does not yet 
> exist, but it will soon. 
>
> If you have any questions, suggestions, or urgently need a permission to 
> release something, let me know -- via email, directly or in this thread, or 
> contact danielbeck in #jenkins on Freenode. 
>
> Daniel 
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20160822/ee8bdcf4/attachment.html>


More information about the Jenkins-infra mailing list