-
Bug
-
Resolution: Fixed
-
Minor
Been seeing this regularly for some time now in Code Valet and other Jenkins environments
java.io.FileNotFoundException: /var/jenkins_home/deployment.out (No such file or directory) at java.io.FileInputStream.open0(FileInputStream.java) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.<init>(FileInputStream.java:138) at java.io.FileInputStream.<init>(FileInputStream.java:93) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar.<init>(AzureVMAgentCleanUpTask.java:138) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$DeploymentRegistrar.getInstance(AzureVMAgentCleanUpTask.java:151) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanDeployments(AzureVMAgentCleanUpTask.java:205) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanDeployments(AzureVMAgentCleanUpTask.java:196) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.clean(AzureVMAgentCleanUpTask.java:571) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.access$200(AzureVMAgentCleanUpTask.java:64) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$3.call(AzureVMAgentCleanUpTask.java:583) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask$3.call(AzureVMAgentCleanUpTask.java:580) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JENKINS-48901] Exception regularly thrown "/var/jenkins_home/deployment.out (No such file or directory)"
Assignee | Original: Azure DevOps [ azure_devops ] | New: Chenyang Liu [ zackliu ] |
Labels | Original: codevalet | New: azure-jenkins codevalet in-progress |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Component/s | New: _unsorted [ 19622 ] | |
Component/s | Original: azure-vm-agents-plugin [ 21950 ] |
We serialize deployment info, so this exception will be thrown the first time used the plugin or the first time updated to new version.
Does this exception being thrown in later use?