-
Bug
-
Resolution: Fixed
-
Blocker
-
-
Blue Ocean 1.1-beta4, Blue Ocean 1.1
The Blue Ocean link from the classical view should be customizable by plugins. Plugins should be able to define or override the url mapping for a given ModelObject.
Also by default this link should take into account when an organization has been defined and if this organization root Item is different from the root of the Jenkins instance
[JENKINS-44208] Make Blue Ocean link url resolution extensible by plugins and take into account Organizations
| Description |
Original:
The "Try Blue Ocean" button goes to the Blue Ocean url defined by BlueOceanWebURLBuilder|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/BlueOceanWebURLBuilder.java#L70] this behaviour is not extensible and there is no way to define URLs for other Items. Also when you are in the classical view inside a folder that is the root item of an org, you should go to /blue/organization/org_name/ instead of /blue/ which could easily be done when this is extensible |
New:
The "Try Blue Ocean" button goes to the Blue Ocean url defined by [BlueOceanWebURLBuilder | https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/BlueOceanWebURLBuilder.java#L70] this behaviour is not extensible and there is no way to define URLs for other Items. Also when you are in the classical view inside a folder that is the root item of an org, you should go to {{/blue/organization/org_name/}} instead of {{/blue/}} which could easily be done when this is extensible |
| Summary | Original: Blue Ocean button url should be extensible and take into account the organization | New: Blue Ocean button url should take into account organization root GroupItem |
| Description |
Original:
The "Try Blue Ocean" button goes to the Blue Ocean url defined by [BlueOceanWebURLBuilder | https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/BlueOceanWebURLBuilder.java#L70] this behaviour is not extensible and there is no way to define URLs for other Items. Also when you are in the classical view inside a folder that is the root item of an org, you should go to {{/blue/organization/org_name/}} instead of {{/blue/}} which could easily be done when this is extensible |
New:
The "Try Blue Ocean" button goes to the Blue Ocean url defined by [BlueOceanWebURLBuilder | https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/BlueOceanWebURLBuilder.java#L70] this When you are in the classical view inside a folder that is the root item of an org, you should go to {{/blue/organization/org_name/}} instead of {{/blue/}} which could easily be done when this is extensible This behaviour is not extensible and there is no way to define URLs for other Items not taken into account by [BlueOceanWebURLBuilder | https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/BlueOceanWebURLBuilder.java#L70] |
| Labels | New: cloudbees-internal-steel |
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
vivek Yes, for Jobs, Runs and Multibranches, for the rest will return null URL which defaults to /blue without org.
alobato Ah, this we can fix easily if we handle instance of ModifiableTopLevelItemGroup. ModifiableTopLevelItemGroup maps to BlueOrganization, which is handled via OrganizationFactory extension, so this should just work in your case.
| Assignee | New: Vivek Pandey [ vivek ] |
alobato I am trying to understand this, so when you are in org folder and click on 'Try Blue Ocean', then it redirects to /blue URL?
Looking at the code, BlueOceanWebURLBuilder is computing org name using OrganizationFactory.], In this case if it can find OrganiationResolver then it can compute url correctly.