-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
-
Blue Ocean 1.6 - beta 2, Blue Ocean - 1.6 - beta 4
Currently there are multiple JS modules in BlueOcean. The development experience/release process of these JS modules, specially jenkins-design-language and blueocean-core-js.
Key goals of this ticket should be:
- Simplified development process so that current pain of releasing and patching package.json across blueocean frontend modules are minimized
- External plugin developers, who extend/build on top of BlueOcean should get npm released version with each blueocean release (including beta)
Deliverables:
- Design/proposal document
- Working code with implementation and release process
- Migration document (good to discuss it during design phase)
- is blocked by
-
JENKINS-47568 POST-JENKINS-42602: move core-js i18n to core-js plugin
-
- Open
-
[JENKINS-49637] Simplify BlueOcean JS development experience
Epic Link | New: JENKINS-40392 [ 177055 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Link | New: This issue is blocked by JENKINS-47568 [ JENKINS-47568 ] |
Sprint | Original: Blue Ocean 1.5 - beta 2 [ 481 ] | New: Blue Ocean 1.5 - beta 3 [ 491 ] |
Rank | New: Ranked higher |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Sprint | Original: Blue Ocean 1.5 - beta 3 [ 491 ] | New: Blue Ocean 1.6 - beta 1 [ 531 ] |
Rank | New: Ranked lower |