Gitlab-plugin: If BlueOcean is installed, build URL does not point to BlueOcean

[jkdeveyra]

Issue

Context

• Gitlab plugin version: 1.4.5
• Gitlab version: 8.4.3
• Jenkins version: 2.45
• Job type: Multibranch Pipeline
• BlueOcean version: 1.0.0-b24

Problem description

When I visit the build link in Gitlab:

it points to the classic Jenkins build URL:

instead of opening the link in BlueOcean:

[omehegan]

Well, I can see why. The plugin tells GitLab what the URL should be to refer back to the build. The Blue Ocean URL is going to be different. And given that a user can switch in and out of the Blue Ocean view at will, I don't see a great way to change this. Just detecting that you have the plugin installed does not necessarily mean that you are using it in all cases. It's still in beta because not all necessary features are implemented in it yet. Also, different users of the same Jenkins install may prefer to use the old view or Blue Ocean.

@i386 this is an interesting situation. Do you have any thoughts on how we should approach it, now or in the future?

[i386]

@omehegan I filed a PR for this but I am not sure if I found all the right places. Should be enough to go on if you want to continue :)

[omehegan]

This has just been released in plugin version 1.5.2. It will be in the update center within a few hours.

[Eldadc]

This has just been released in plugin version 1.5.2. It will be in the update center within a few hours.

Hi,
Is it possible to control which Jenkins view can be opened ? I want my classic to be opened and Blue-ocean view is the now my default view.
Thanks In Advanced,