-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper #3
Comments
We are also seeing exactly this behaviour using the plugin on Jenkins v1.580.1 and it is a significant issue for us. Not sure if the workaround to execute the job on MASTER will work, but ideally we don't want to do that. We can probably use the Package Manager API directly too, but again, would prefer not to. Any ETA on when there might be a fix ?? |
Also having the same issue, anyone resolved this yet? |
You may be using the wrong package filter format. Try to wildcard the group and version. :: |
Hi David, |
This happens when using Jenkins ver. 1.607.
Related Error messages:
ERROR: Failed to list package files: remote file operation failed
FATAL: No package found matching filter *.zip
java.io.IOException: No package found matching filter *.zip
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.selectPackages(DeployPackagesBuilder.java:338)
at org.jenkinsci.plugins.graniteclient.DeployPackagesBuilder.perform(DeployPackagesBuilder.java:259)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
at hudson.model.Build$BuildExecution.build(Build.java:203)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
The text was updated successfully, but these errors were encountered: