[JIRA] (JENKINS-55311) Blue Ocean: Pipeline editor always assumes "main" branch is named master

2 views

Skip to first unread message

dirk.heinrichs@recommind.com (JIRA)

unread,

Dec 22, 2018, 7:44:02 AM12/22/18

to jenkinsc...@googlegroups.com

Dirk Heinrichs created an issue

Jenkins /

JENKINS-55311

Blue Ocean: Pipeline editor always assumes "main" branch is named master

Issue Type:	Bug
Assignee:	Unassigned
Components:	blueocean-pipeline-editor-plugin
Created:	2018-12-22 12:43
Environment:	Linux
Priority:	Major
Reporter:	Dirk Heinrichs

Blue Ocean pipeline editor is not usable with Git when master branch has been renamed. Seems it always assumes the main branch is named master, which doesn't need to be the case. If it's not, it creates a new branch from the root of the repository tree instead of asking which branch to branch off from. As a result, the repository will contain two distinct trees, one with the already checked in sources, the other one with just the new Jenkinsfile.