On Thu, Apr 26, 2018 at 5:08 PM, Alex Harui
wrote:
> On 4/26/18, 2:57 PM, "Greg Stein" wrote:
> On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
>
> > On Thu, Apr 26, 2018, 15:06 Alex Harui
> wrote:
> >
> >> Perhaps I wasn't clear. I am not concerned about Jenkins projects
> bei
>> > varying activity levels and thus may have jobs that are idle for
>> years and
>> > it can be helpful to keep at least the last build around as a
>> reference in
>> > case the next time we run the build there is a failure. Please
roducts”
>> with
>> > varying activity levels and thus may have jobs that are idle for
>> years and
>> > it can be helpful to keep at least the last build around as a
>> reference in
>> > case the next time we run the build there is a failure.
d thus may have jobs that are idle for
> years and
> > it can be helpful to keep at least the last build around as a
> reference in
> > case the next time we run the build there is a failure. Please
> notify us
> > if we miss limiti
ng the number of old builds. I think I fixed the ones
> that didn’t have limits. But there does seem to be folders left around
for
> builds I think we deleted.
>
> Thanks,
> -Alex
>
>
> From: Chris Lambertus
> Reply-To:
&
uilds I think we deleted.
>
> Thanks,
> -Alex
>
>
> From: Chris Lambertus
> Reply-To:
> Date: Wednesday, April 25, 2018 at 12:04 AM
> To:
> Subject: Re: purging of old job artifacts
>
>
>
>
> On Apr 24, 2018, at 8:04 PM, Allen Wittenauer mailto:a...@ef
From: Chris Lambertus
Reply-To:
Date: Wednesday, April 25, 2018 at 12:04 AM
To:
Subject: Re: purging of old job artifacts
On Apr 24, 2018, at 8:04 PM, Allen Wittenauer
mailto:a...@effectivemachines.com>> wrote:
On Apr 24, 2018, at 5:01 PM, Greg Stein
mailto:gst...@gmail.com&g
On Wed, Apr 25, 2018 at 9:49 AM, Allen Wittenauer
wrote:
>...
> I apologize. I took Greg’s reply as Infra’s official “Go Pound
> Sand” response to what I felt was a reasonable request for more information.
>
It was "Please stop asking ChrisL for more work. The todo work is upon
users of
Yeah, fwiw, any build that doesn't have a build.xml (and therefore can't be
loaded by Jenkins/displayed in the UI/etc) or any job directory that
doesn't have a config.xml should just be rm'd. That's just eating disk
space with no way of being used.
A.
On Wed, Apr 25, 2018 at 11:07 AM, Chris Lambe
> On Apr 25, 2018, at 7:49 AM, Allen Wittenauer
> wrote:
>
>> Using the yetus jobs as a reference, yetus-java builds 480 and 481 are
>> nearly a year old, but only contain a few kilobytes of data. While removing
>> them saves no space, they also provide no value,
>
> … to infra.
>
>
> On Apr 25, 2018, at 12:04 AM, Chris Lambertus wrote:
>
> The artifacts do not need to be kept in perpetuity. When every project does
> this, there are significant costs in both disk space and performance. Our
> policy has been 30 days or 10 jobs retention.
That policy wasn’t always
> On Apr 25, 2018, at 3:04 AM, Chris Lambertus wrote:
>
> The top-level list of jobs is available here: https://paste.apache.org/r37e
>
That list includes:
• CXF-2.0-deploy
• CXF-2.0.x-JDK15
• CXF-2.1-deploy
• CXF-2.1.x-JDK15
Those jobs were deleted from Jenk
> On Apr 24, 2018, at 8:04 PM, Allen Wittenauer
> wrote:
>
>
>> On Apr 24, 2018, at 5:01 PM, Greg Stein wrote:
>>
>> Let's go back to the start: stuff older than six months will be deleted.
>> What could possibly need to be retained?
>
> - Not every job runs every day. Some are extr
> On Apr 24, 2018, at 5:01 PM, Greg Stein wrote:
>
> Let's go back to the start: stuff older than six months will be deleted.
> What could possibly need to be retained?
- Not every job runs every day. Some are extremely situational.
- Some users might have specifically marked
Let's go back to the start: stuff older than six months will be deleted.
What could possibly need to be retained?
Assume all jobs will be touched.
On Tue, Apr 24, 2018, 18:32 Allen Wittenauer
wrote:
>
> > On Apr 24, 2018, at 4:27 PM, Chris Lambertus wrote:
> >
> > The initial artifact list is
> On Apr 24, 2018, at 4:27 PM, Chris Lambertus wrote:
>
> The initial artifact list is over 3 million lines long and 590MB.
Yikes. OK. How big is the list of jobs? [IIRC, that should be the
second part of the file path. e.g., test-ulimit ] That’d give us some sort of
scope, who is
> On Apr 24, 2018, at 4:23 PM, Allen Wittenauer
> wrote:
>
>
>> On Apr 24, 2018, at 4:13 PM, Chris Lambertus wrote:
>>
>> If anyone has concerns over this course of action, please reply here.
>
> Could we get a list?
>
> Thanks!
>
The initial artifact list is over 3 million
> On Apr 24, 2018, at 4:13 PM, Chris Lambertus wrote:
>
> If anyone has concerns over this course of action, please reply here.
Could we get a list?
Thanks!
Hi builders,
We are in the initial phases of speccing out a replacement Jenkins server using
NVMe disks for improved performance. At this time, the jobs/ directory on
jenkins-master has artifacts dating back to at least 2012, and these artifacts
are taking up a considerable amount of space on
19 matches
Mail list logo
