I know too little about Jenkins to know how to apply this solution, but I can try to help. The Solr jobs are defined in Jenkins, not in our repo in Jenkinsfile. Maybe you could apply this to one of the jobs yourself? Does this need to be done on all jobs or just some or will just one do?
On Fri, Jul 3, 2026 at 8:20 AM Bob Thomson <[email protected]> wrote: > This has come up as an issue again today, necessitating intervention to > keep the service available. > > On 2026/06/29 07:04:23 Robert Thomson wrote: > > Hi, > > > > We are regularly noticing a build-up of large ws-cleanup directories > > on lucene3 and 4, necessitating deletion. Camel also experiences this > > issue with builds and the root cause is that there are files created > > as part of the docker build that are not owned by the user used for > > the cleanup, so fail to be deleted by the workspace clean up plugin. > > > > Searching with GenAI came up with the following suggestion when > > discussing with them that you may like to try out in your pipelines > > that create docker images. > > > > Kind regards, > > -Bob Thomson, > > ASF Infrastructure > > > > post { > > always { > > // Fallback option: If standard cleanWs() stalls out on > permissions > > script { > > try { > > cleanWs deleteDirs: true, disableDeferredWipeout: true > > } catch (Exception e) { > > echo “Standard cleanup failed, launching Docker Root > > Purge force-override...” > > sh “”" > > docker run --rm \ > > -v ${WORKSPACE}/..:/zap \ > > alpine:latest \ > > sh -c ‘rm -rf /zap/*-ws-cleanup*’ > > “”" > > } > > } > > } > > } > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
