Hi I have a task that needs a lot of time. To not occupy Jenkins for days I made it like this that the task is started via cron on the agent, without Jenkins. In the end a Jenkins job is started to just get the results which is a matter of seconds. My problem is now that sometimes the workspace on the node is completely wiped, sometimes even while the task is running which of course then makes it fail. But I couldn't find a reason why this would happen. It's exactly the workspace as defined in the Jenkins job that is cleared, not just the (sub)directory where my task is running. What are the reasons that Jenkins might do that? I've seen it happen before checking out from a version control system if the workspace was not yet a checkout. But there's no checking out in the job anymore. Could it be that if the connection to the node is lost and reestablished that some cleaning or setting up is done? Are there any other reasons that Jenkins (agent) might clean the workspace, completely out of sync with any running job?
Thanks bye Fabi -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20220405063528.AADDF4B4A9BC%40macserver.private.