Hello Mark, >From my PoV, this access can be granted for this project. It has to be *temporary* as Darin is not part of the infra team. I would prefer for the next such occurrence, to have the infra team working on it, to reduce the need to grant permission to other people. The permissions are pretty powerful in terms of potential of damage, so limiting them to only few people with the need is required.
Wadeck On Wednesday, February 5, 2025 at 5:35:43 AM UTC+1 Mark Waite wrote: > On Tuesday, January 28, 2025 at 8:39:30 PM UTC-7 Mark Waite wrote: > > JFrog sponsors the Jenkins artifact repository at > https://repo.jenkins-ci.org. They've asked us to reduce our storage > usage from the current 9+ TB to fit within their hosting guidelines of less > than 5 TB of artifacts per sponsored open source project. > > Darin Pope has agreed to lead a project to reduce our artifact storage > requirements. He will work with Damien Duportal as needed to plan the > project, perform experiments, run test brownouts, and resolve issues. > > Darin will need administrator access to the artifact repository while he's > working on this project. > > Any concerns from the security team or from others if Darin is given > administrator access to https://repo.jenkins-ci.org while working on the > project? > > > Darin suggested that he first be given write access to the incrementals > tree so that he can create the cleanup script that removes older > incremental artifacts. Wadeck and Damien is that OK with you? > > Mark Waite > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/4ebd2909-ef16-434d-a841-0937981f5da8n%40googlegroups.com.
