Random delete failures after upgrading Jenkins

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Random delete failures after upgrading Jenkins

Randy Beckwith

We recently upgrade to Jenkins 2.284 and Perforce plugin version 1.11.3.


Since then our jobs are experiencing frequent

                P4: Task Exception: java.io.IOException: Unable to delete file: c:\j\esi-par\dev


During the ‘rm -rf c:\j\esi-par\dev’ of the P4 sync, just prior to the actual sync operation.


This directory did not exist prior to the start of the Jenkins job. It’s the directory for the Jenkins workspace. Our Jenkins agents are managed by the vSphere plugin. When the job is about to start the vSphere plugin reverts the agent to a base snapshot. The directory does not exist in that base snapshot.


These delete issues did not occur prior to the Jenkins upgrade and they don’t always occur.


I was wondering if anyone else has experienced anything like this.



Randy Beckwith

Senior Software Engineer, NIA Platform Group



[hidden email]

nexidia.com | twitter | youtube | linkedin | facebook


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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/BN6PR12MB1379A36DDF9C074AC03CF007BC649%40BN6PR12MB1379.namprd12.prod.outlook.com.