Add Blue Ocean to the managed set

[basil]

No description provided.

[basil]

Blocked on the release of this

[jtnord]

Why would you want to consider this?

• BlueOcean has long been deprecated, builds do not work on modern ARM platforms or windows.
• The interesting pars of BO are written in javascript and are not tested as part of the PCT.
• BlueOcean itself is not extensible, so depending on it in a plugin is questionable.

[timja]

blue-ocean-rest at least is used in a few plugins:
https://github.com/search?q=org%3Ajenkinsci%20blueocean-rest&type=code

e.g. https://github.com/jenkinsci/azure-storage-plugin/blob/b575d77fa397e57dfe50eb8d7da7d10b6b480e03/pom.xml#L82-L86

[MarkEWaite]

Why would you want to consider this?

When @basil and I discussed it, he noted that by placing blue ocean into the plugin bill of materials we can detect issues earlier. The benefit was focused more on early detection of issues than on assisting other plugins with managing their dependencies.

[basil]

https://github.com/jenkinsci/bom/blob/master/README.md#when-to-add-a-new-plugin

[basil]

This change is already proving valuable, as I have found a bug in a different project that I would not have discovered had I not been running PCT against Blue Ocean from day 1

[MarkEWaite]

I would like to release a new version of the plugin bill of materials mid-week this week, rather than wait until the end of the week. The new release would include the addition of the blue ocean plugins, the maven plugin, and the conditional build step plugin. Several useful updates have also arrived since the previous release.

Does that work for you @basil ? Any compelling reason for me to wait until end of the week to do the release?

[basil]

Sure, sounds good