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]
