Re: Artifact storage reduction project

2025-02-07 Thread Damien Duportal
Quick addendum as my previous message is unclear: - Temporary access to only the incremental repo. for Darin is a good idea to limit the impact of extended permissions (e.g. the risk of a human mistake removing things). It's safer for a first step! - The low "impact" I mentioned was

Re: Artifact storage reduction project

2025-02-07 Thread Damien Duportal
It's a +1 for me if it is a temporary access as stated by Wadeck in the above message. The rationale is that the infra team is busy on other tasks with the same level of priority (ci.jenkins.io migration to AWS + FOSDEM) hence Mark's proposal to have temporary help. Darin has the skillset and r

Re: Artifact storage reduction project

2025-02-07 Thread 'wfoll...@cloudbees.com' via Jenkins Developers
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

Re: Artifact storage reduction project

2025-02-04 Thread Mark Waite
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 spon

Artifact storage reduction project

2025-01-28 Thread Mark Waite
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