Open timja opened 8 years ago
Mercurial Plugin still depends on SCM API 0.1. These extension points were added in 0.3. So it should be possible setting up a Jenkins 1.651.1 install with Mercurial Plugin, manually downgrade SCM API to 0.2, restart, everything works, upgrade to 2.0 RC, install Pipelines, expect it to explode.
Reproducible by installing the latest weekly, then installing 2.0 RC on top of it, then installing these plugins. Will show a similar error for Credentials Plugin.
As Jenkins is showing the update center install progress screen, and tells people to restart, I don't think this is particularly critical. It's certainly not nice, but we're working on this behavior in the context of JENKINS-21486, JENKINS-34073 (which barely got pulled out of 2.0 due to risk of perceived regressions).
Reported on IRC:
My guess: The old dependency system (
JENKINS-21486) does not take into account that dependencies may exist but be outdated when trying to dynamically load a plugin.In the case of an outdated SCM API plugin (judging from these messages), this results in exceptions upon Pipeline plugin installation.
Originally reported by danielbeck, imported from: Pipeline plugin installs in upgrade wizard throws exceptions