-
Bug
-
Resolution: Fixed
-
Blocker
-
-
Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2
Since the move to hpi based jdl et. al. custom plugins are forced to sync any given dependency that is coming from BO in your plugin package.json so that you use the *exact* version as BO does.
If not you get blank screen and some error of "0 of undefined" and then you see e.g. "react-router" involved so you need to look into your version and theirs of "react-router".
Once you have it, you have to keep the dependency of BO on your watch to adopt when they do.
Prior to the change the dep resolving did neither worked correctly in returning you the version BO uses and not the one you requested but at least in 90% of the cases the plugin would have still worked.
The problem here as I see it, is it forces plugin developer to release plugins on a fixed BO version and every time BO does a new release, meaning keeping backward compatibility is becoming impossible.
- relates to
-
-
- Closed
-
[JENKINS-47673] Current BO Master forces third party bo based plugins to use the exact versions of npm deps
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
| Assignee | New: Keith Zantow [ kzantow ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
michaelneale no, in the past we had latent bugs because we had multiple things bundled and duplicated objects being passed around in unexpected ways.
kzantow so is resolvable ?- ie it won't fuss if the third party plugin deps don't match up 100%?
| Epic Link | New: JENKINS-35749 [ 171790 ] |
tscherler yes, if this is the case, this does seem bad (ie in the past you didn't quite get the version you wanted right, but you would get "a version" right?)