Shared Libraries fail with java.lang.NoSuchFieldError: workspace error after an upgrade

Last Reviewed:2025-04-07()
1 minute readKnowledge base

Issue

  • After upgrading my CloudBees CI controller, all Pipelines fail to use Shared Libraries with the following error:

java.lang.NoSuchFieldError: workspace at PluginClassLoader for workflow-cps-global-lib//org.jenkinsci.plugins.workflow.cps.global.GroovyShellDecoratorImpl$1.configureShell(GroovyShellDecoratorImpl.java:30) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsGroovyShellFactory.build(CpsGroovyShellFactory.java:125) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:649) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:598) at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:343) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) [withMaven] downstreamPipelineTriggerRunListener - Failure to introspect build steps: java.io.IOException: <my-job> #425 did not yet start [withMaven] downstreamPipelineTriggerRunListener - Failure to introspect build steps: java.io.IOException: <my-job> #425 did not yet start Finished: FAILURE

Context

The Pipeline: Deprecated Groovy Libraries plugin depends on the Git server plugin. The enhancements made to the Git Server plugin in #134, made older versions of the Deprecated Groovy Libraries plugin incompatible. #214 was merged to adapt the deprecated plugin to the new Git Server implementation.

Resolution

There are two solutions possible for this issue, the first being the recommended one:

Tested product/plugin versions

  • CloudBees CI on traditional platforms - operations center and client controller version 2.492.3.5.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.