-
Bug
-
Resolution: Unresolved
-
Minor
-
-
Blue Ocean - Candidates
When one of the Jenkins folders in a folder hierarchy itself is named "pipelines" and also contains build pipelines (as code), the blue ocean plugin comes up with an empty page. Upon examination with Chrome developer tools, it became apparent that the first "pipelines" token, in the URL for getting a list of pipelines for a folder, that happens to be the Jenkins folder name and not the "pipelines" REST resource is actually being interpreted as the "pipelines" REST resource.
This results in a 404 and no pipelines are displayed by the BlueOcean plugin. When I changed the offending folder name to pipelines-01, the issue went away.
akabraab thanks for reporting. We will investigate shortly.