On Thu, Apr 26, 2018 at 5:08 PM, Alex Harui <aha...@adobe.com.invalid> wrote:
> On 4/26/18, 2:57 PM, "Greg Stein" <gst...@gmail.com> wrote: > On Thu, Apr 26, 2018, 16:42 Greg Stein <gst...@gmail.com> wrote: > > > On Thu, Apr 26, 2018, 15:06 Alex Harui <aha...@adobe.com.invalid> > wrote: > > > >> Perhaps I wasn't clear. I am not concerned about Jenkins projects > being > >> removed, just the artifacts of those projects. I am trying to make > two > >> points: > >> > >> 1) Old artifacts might have value as a known good build for a job > that > >> may not get run for years. So please don't run a clean up that > deletes all > >> artifacts older than N days. > > > > Nope. Download those artifacts if you want to keep them. The Jenkins > > Master is not an archival system. It exists for our projects to do > builds. > > We have identified the overabundance of old artifacts as detrimental > to the > > service, which affects everyone. > > To be clearer here, Chris earlier said/asked: > we’d ask that this be exported and managed locally by the project > rather > than remaining “live” on the master. Is there a reason other than > convenience for it to remain live? > > I thought we were allowed to provide feedback instead of following strict > orders against old artifacts. Sigh. And there is the "us vs them" crap again. This is not about "following strict orders" from Infra. Yes, feedback is and has been requested, and discussion even better. So: provide that ... is there a good reason to keep the artifacts there? That is the entire nature of Chris' original email. "We need to delete these to improve the service. Is there a concern/reason we should not?" And that has not been answered. Sorry for my misunderstanding. For sure, lots of resources are being > consumed by old artifacts. I was just hoping we could save one old build > per Jenkins project regardless of age for convenience. But if not, I guess > we will take the time to figure out where to store it and document where we > put it. I guess we have to create a repo for these so it isn't under some > committer's home.a.o account or on somebody's machine. Or is there other > ASF shared storage I'm not remembering? > You've listed them. We don't have a generalized, unversioned file storage mechanism. home.a.o is likely the best. Even if the committer who uploads them goes AWOL, they'll still remain accessible. Will old files in Jenkins workspaces for projects also get purged over time? > Somebody else will need to answer this. I dunno if we're purging old files from the workspaces, or how that is different from what *is* being purged. Cheers, -g
