On Mon, Apr 11, 2022 at 2:05 PM Fabian Cenedese <[email protected]> wrote:
> At 13:53 11.04.2022, you wrote: > > >Workspaces Jenkins considers "unused" are wiped periodically. While this > is intended to be safe, i.e., never delete the last workspace, or > workspaces of running builds, it's not impossible that "active" workspaces > are caught in rare circumstances. Check the workspace cleanup log in your > Jenkins home to see whether this happens to you, or enable detailed (FINE) > logging for the logger "hudson.model.WorkspaceCleanupThread". > > Thanks for the info, that's what seems to be happening. I'll see if I can > check this in case it happens again. Is this something that can be > influenced in the settings or is it completely automatic? Would I need > to run a job more often to prevent this? Or I could put all my files in > a different directory outside the workspace and change into it in > the job. That way there's nothing to delete in the configured workspace. > This is completely automated and invisible beyond log entries (probably not great). While there are some possible approaches to stop Jenkins from doing that when it occurs with regular Jenkins jobs, your situation is different. In your particular case, you're using what amounts to a Jenkins-managed resource outside Jenkins. The cleanest solution is what you suggest: to stop doing that, run your cron job somewhere else, and limit Jenkins workspace use to actual Jenkins jobs. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMo7Pt%2BxqNi77CWva8KtkCcwNMsGrjkd6qJRR5nH_16KG4sq2Q%40mail.gmail.com.
