-
Bug
-
Resolution: Fixed
-
Major
-
jenkins-2.1
During fixing of JENKINS-34669 I've discovered that Jenkins 2.1 bundles the obsolete version of jenkins-js-builder. The last release version is 0.0.51, but Jenkins core still bundles 0.0.40. It means the core does not get patches like this one: https://github.com/tfennelly/jenkins-js-modules/commit/dd98ceefcc28861b11272214aeb9bc32a3aaae62
This fix is required to prevent fatal failures on module duplicates
Background
We have a plugin, which tweaks Jenkins UI before the startup in order to initialize some stuff (add extra plugins, etc.). So the plugin has an additional UI page. When I bundle this plugin into Jenkins.war, Jenkins 2.0 installation Wizard hangs infinitely. According to the JS debugger, it happens due to the ""Jenkins global module 'pluginSetupWizard' already registered." error. There are stacktraces for the first and second export operations. Jenkins WebUI should at least return an error for such failures. Ideally it should be robust agains such "hacks in plugins"
- is related to
-
-
- In Progress
-
-
JENKINS-34990 Update js-modules to latest versions published in @jenkins-cd org
-
- Open
-
- links to
[JENKINS-34676] Duplicate include of pluginSetupWizard.js
| Labels | New: jenkins2.0 regression |
| Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Remote Link | New: This issue links to "jenkins/pull/2320 (Web Link)" [ 14279 ] |
| Description |
Original:
We have a plugin, which tweaks Jenkins UI before the startup in order to initialize some stuff (add extra plugins, etc.). So the plugin has an additional UI page. When I bundle this plugin into Jenkins.war, Jenkins 2.0 installation Wizard hangs infinitely. According to the JS debugger, it happens due to the ""Jenkins global module 'pluginSetupWizard' already registered." error. There are stacktraces for the first and second export operations. Jenkins WebUI should at least return an error for such failures. Ideally it should be robust agains such "hacks in plugins" |
New:
During fixing of JENKINS-34669 I've discovered that Jenkins 2.1 bundles the obsolete version of jenkins-js-builder. The last release version is 0.0.51, but Jenkins core still bundles 0.0.40. It means the core does not get patches like this one: https://github.com/tfennelly/jenkins-js-modules/commit/dd98ceefcc28861b11272214aeb9bc32a3aaae62 This fix is required to prevent fatal failures on module duplicates Background {noformat} We have a plugin, which tweaks Jenkins UI before the startup in order to initialize some stuff (add extra plugins, etc.). So the plugin has an additional UI page. When I bundle this plugin into Jenkins.war, Jenkins 2.0 installation Wizard hangs infinitely. According to the JS debugger, it happens due to the ""Jenkins global module 'pluginSetupWizard' already registered." error. There are stacktraces for the first and second export operations. Jenkins WebUI should at least return an error for such failures. Ideally it should be robust agains such "hacks in plugins" {noformat} |
| Summary | Original: Conflict with a plugin causes hanging of the Jenkins 2 installation Wizard | New: Outdated version of js-modules causes loading issues on JS module conflicts |
| Link | New: This issue is related to JENKINS-34669 [ JENKINS-34669 ] |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
| Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |