-
Bug
-
Resolution: Fixed
-
Minor
Under an strange circumstance, after uploading a credential to Global Credentials section, Jenkins says that the credential is created and it is correct, but physically the file is not uploaded (or it is removed). In these cases the the credentials-binding-plugin fails with next exception:
java.io.IOException: remote file operation failed: /scratch/jenkins/secretFiles/35effc3c-7cfe-4d39-ad01-720f9f0c0913 at hudson.remoting.Channel@18993415:13ca24de: java.io.FileNotFoundException: /scratch/jenkins/secretFiles/35effc3c-7cfe-4d39-ad01-720f9f0c0913 (Is a directory) at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.write(FilePath.java:1881) at hudson.FilePath.copyFrom(FilePath.java:882) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.copy(FileBinding.java:89) at org.jenkinsci.plugins.credentialsbinding.impl.FileBinding.bindSingle(FileBinding.java:60) at org.jenkinsci.plugins.credentialsbinding.Binding.bind(Binding.java:126) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution.start(BindingStep.java:89)
It would be great if the plugin enforce to have a fileName set, and in case of not (probably because the credentials are not there) to throw an exception explaining the situation instead of showing an exception which does not explain this situation.
- links to