Status: Closed (View Workflow)
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
JENKINS-39646 Properly generate bundles for packages that have multiple top-level modules
kzantow this one may be done now the shrinkwrap files went back in right?
- This isn't something that can be tested within Blue Ocean itself, because the problem stems from custom plugins which rely upon, or extend, Blue Ocean itself.
still a WIP - keith working very hard at it.. .this is marked as a blocker and getting the attention it needs.
alobato yes I think the doc explains the problem we see point on.