Status: Closed (View Workflow)
- Standalone git 2.7.4 running on an Ubuntu server
- Core 2.78
- Experimental update center plugins, including Blue Ocean 1.3-beta2
- Beta-5 SNAPSHOTlevel Declarative Pipeline
- Fedora Workstation 26
- Google Chrome 61
Sprint:Blue Ocean 1.3
When connecting to a plain git repository over SSH, which has no Jenkinsfiles in it, attempts to save and create a Jenkinsfile to master will not write the Jenkinsfile. However, attempts to save to a new branch work fine.
- A remote git "server" you can successfully connect to via ssh.
- A repository on same git server, which has been git init'd and has a README.md file on the master branch, but nothing else. The git history looks more or less like this:
Steps to reproduce:
1. Launch Blue Ocean and select New Pipeline.
2. Select Git as your SCM, and provide a valid URL, in the form of ssh://firstname.lastname@example.org/path/to/git-server/repos/repo-name.
3. When Blue Ocean presents you with an SSH key to register with the Git server, do so, by adding it to /home/username/.ssh/authorized_keys
6. Click "Save," provide a commit message, and leave the default setting of "Commit to master" selected. Then click Save & run.
8. Check on the git server, to see if anything was created. Nothing was:
11. And we can see this on the git server, too: