Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results. The pro...
Question
jenkins
#4: Post edited
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
- The problem is, sometimes downloading from Perforce fails:
> 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\...In the error message, P4 is a common abbreviation for Perforce. We have a [Jenkins plugin called P4](https://plugins.jenkins.io/p4/) which downloads files from Perforce; I guess it's this plugin that writes this error message. I think something is holding the file open, that's why it couldn't be deleted.- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
- The problem is, sometimes downloading from Perforce fails:
- `12:46:19 operating system will not allow deletion of file c:\Jenkins\...(redacted)...\p4j5949332513673726584.tmp on client.
- `
- In the error message, P4 is a common abbreviation for Perforce. We have a [Jenkins plugin called P4](https://plugins.jenkins.io/p4/) which downloads files from Perforce; I guess it's this plugin that writes this error message. I think something is holding the temporary file open, that's why it couldn't be deleted.
- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
#3: Post edited
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
- The problem is, sometimes downloading from Perforce fails:
- > 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\...
- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
- The problem is, sometimes downloading from Perforce fails:
- > 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\...
- In the error message, P4 is a common abbreviation for Perforce. We have a [Jenkins plugin called P4](https://plugins.jenkins.io/p4/) which downloads files from Perforce; I guess it's this plugin that writes this error message. I think something is holding the file open, that's why it couldn't be deleted.
- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
#2: Post edited
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
To prevent confusion, the Jenkins job deletes all files from the target directory before downloading the scripts. The problem is, sometimes this fails:- > 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\...
- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
- We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results.
- The problem is, sometimes downloading from Perforce fails:
- > 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\...
- What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this?
- Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?
#1: Initial revision
Jenkins failed to delete a file - why? How to prevent?
We are using Jenkins to run our system tests on a regular schedule. The Jenkins job downloads some python scripts from Perforce, runs them and compares the outputs with known-good results. To prevent confusion, the Jenkins job deletes all files from the target directory before downloading the scripts. The problem is, sometimes this fails: > 20:29:53 P4 Task: failed: java.io.IOException: Unable to delete file: c:\Jenkins\blahblah\... What can I do to prevent this? I imagine that it can be caused by an antivirus, some person quietly browsing in the Jenkins's file system, a random cosmic ray, etc. How can I even start investigating this? Did we do something fundamentally wrong in configuring our Jenkins job this way? Something which would completely prevent this issue from happening?