Status: Resolved (View Workflow)
OS: Windows Server R2 2008 Fundation (x64)
Jenkins Version : Jenkins ver. 2.121.3 LTS
- - Blue Ocean 1.8.2
- - Blue Ocean Pipeline Editor 1.8.2
When the pipeline is located in the main view (root) of the Jenkins, from the Blue Ocean Dashboard you can access the Visual Pipeline Editor
The pen is displayed in the top menu and allows access to the Pipeline edition.
When the pipeline is moved inside a Folder (CloudBees Folders Plugin), the pen disappears to access the Pipeline edition.
The issue seems to be right here in loadPipelineMetadata(), loadBranchMetadata() and save(...) when the / is used for splitting and group 0 assumed to be the team:
const split = pipeline.split('/'); const team = split; (const repo = split;)
which is used as a pipeline name here:
A simple fix might be to use every element of the split except for the last one for the team and the last element for the repo. Not sure if this might break something else. But from a quick overview of the code it does not look like it
Here it seems to be implemented correctly with the branch name being spliced of the end of the pipeline name: https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-editor/src/main/js/PipelineEditorLink.jsx#L33
Pull Request: https://github.com/jenkinsci/blueocean-plugin/pull/2217
Bump? Seems like an easy thing to fix (I hope) in order to make Blue Ocean much more valuable to us. It's been almost 2.5 years since this was posted, and this minor but meaningful bug is still ... well, bugging us.
Put another way, the following process sucks:
I know this is a small bug, but I would certainly like it addressed. The above process just sucks too much - it makes me almost want to just toss Blue Ocean altogether, in spite of its obvious value, when I have a lot of work going on in Jenkins.
Thanks for considering this.