Hello Chris,
could you please take a look at
https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings
It has rule to keep 3 last builds, but somehow it keeps 5
Manual delete fails with stacktrace:
ava.io.IOException: openmeetings #2860:
/x1/jenkins/jenkins-home/jobs/openmeetings/bui
Hmm. Upon further investigation, I do see that the
pulsar-master/modules/*/builds directories contain current builds between 13
and 15 June, and then hundreds of builds from 2018 and 2017. It looks like
these are indeed “orphaned” builds, and your ‘discard old builds’ configuration
is working p
Hi Chris,
sorry, I lost the updates on this thread.
After applying the "discard old builds" check, I saw all the old stuff
going away. Even now I don't see any of the old builds, from the
Jenkins UI.
https://builds.apache.org/job/pulsar-master/
Is it possible that maybe Jenkins failed to cleanup
All,
Thanks to those who have addressed this so far. The immediate storage issue has
been resolved, but some builds still need to be fixed to ensure the build
master does not run out of space again anytime soon.
Here is the current list of builds storing over 40GB on the master:
597GPackag
I deleted 3 FlexJS builds that we haven’t used in a year and a half.
On 6/10/19, 2:29 PM, "Chris Lambertus" wrote:
Matteo,
pulsar-website cleaned up nicely. pulsar-master is still problematic -
despite having run a few minutes ago, there are still builds dating back to
2017 in th
Matteo,
pulsar-website cleaned up nicely. pulsar-master is still problematic - despite
having run a few minutes ago, there are still builds dating back to 2017 in the
pulsar-master/modules/org.apache.pulsar* directories, so it also appears that
maven module ‘discard old builds’ is not working e
Outstanding, thanks. I believe the job cleanup runs when the next build runs.
You could manually trigger a build to test, or we can check next time the build
runs automatically (presuming it runs nighty.)
-Chris
> On Jun 10, 2019, at 11:10 AM, Matteo Merli wrote:
>
> For pulsar-website-build
For pulsar-website-build and pulsar-master, the "discard old builds"
wasn't set unfortunately. I just enabled it now. Not sure if there's a
way to quickly trigger a manual cleanup.
Regarding "pulsar-pull-request": this was an old Jenkins job no longer
used (since we switched to multiple smaller PR
Hello,
The jenkins master is nearly full.
The workspaces listed below need significant size reduction within 24 hours or
Infra will need to perform some manual pruning of old builds to keep the
jenkins system running. The Mesos “Packaging” job also needs to be corrected to
include the project
