Jenkins "requires a restart" - Plugin Dependency Not Yet Active

By Kaveh Alemi·Latchkey

A plugin was installed (or updated) but is not yet active because Jenkins has not restarted, or one of its required dependency plugins is missing or too old. Its pipeline steps and features remain unavailable until the controller restarts with the dependency satisfied.

What this error means

After installing a plugin, its step still fails with "No such DSL method", or the Plugin Manager shows the plugin needing a restart or flagging an unmet/older dependency. The feature does not work until Jenkins restarts and loads the plugin and its dependencies.

Plugin "pipeline-utility-steps" is installed but requires a restart to take effect
# or
Dependency "workflow-cps" (2.94) is older than required (3.x) - plugin not loaded

Common causes

Plugin installed but controller not restarted

Many plugins only become active after a controller restart. Until then their classes and steps are not registered, so the new functionality is missing.

Unmet or outdated dependency plugin

A plugin requires another plugin at a minimum version. If that dependency is missing or too old, Jenkins refuses to load the plugin, leaving its steps unavailable.

How to fix it

Restart with dependencies satisfied

1. Use "Download now and install after restart" then perform a safe restart so the plugin loads.
2. Resolve unmet dependencies in the Plugin Manager - install/upgrade the required plugins to the listed minimum versions.
3. After restart, confirm the plugin shows enabled and its step resolves (Snippet Generator lists it).

Manage the full plugin set as code

Pin the plugin and all its dependencies together so every controller loads a tested, consistent set.

# plugins.txt (managed by JCasC / install-plugins)
pipeline-utility-steps:2.16.2
workflow-cps:3853.vb_a_490d892963
credentials-binding:681.vf91669a_32e45

How to prevent it

• Install/upgrade plugins with their dependencies and restart in a maintenance window.
• Manage plugins as code so dependency versions stay consistent and complete.
• Verify a new step resolves after restart before relying on it in pipelines.

Frequently asked questions

Related guides

References

• GitHub Actions documentation