-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins, Blue Ocean, and Pipeline:
- 1.3.0-beta-3-SNAPSHOT (private-d6b77636-kshultz)
- Core 2.78
- Declarative 1.2-beta5
- Experimental update center active
SCM:
- Plain Git 2.7.4 over SSH
Client:
- Fedora Workstation 26, on a Dell XPS13 with a 4K display. It's a 13" screen at 3200x1800 resolution
- Google Chrome 61Jenkins, Blue Ocean, and Pipeline: - 1.3.0-beta-3-SNAPSHOT (private-d6b77636-kshultz) - Core 2.78 - Declarative 1.2-beta5 - Experimental update center active SCM: - Plain Git 2.7.4 over SSH Client: - Fedora Workstation 26, on a Dell XPS13 with a 4K display. It's a 13" screen at 3200x1800 resolution - Google Chrome 61
-
-
Blue Ocean 1.3, Blue Ocean - Candidates
Summary:
After setting up a new remote repository for the first time, when that repo has no Jenkinsfile in it, the user is taken to the "You don't have any branches that contain a Jenkinsfile" message, and given the option to Create a Pipeline. Once in the editor, if the user changes his or her mind and clicks the "Go to classic" button, a 404 will appear.
Frequency of occurrence:
100%
Steps to recreate:
1. Successfully connect to a remote Git repo which has n Jenkinsfile in it. I was doing this to verify the fix (still not merged) for JENKINS-46885. The remote repo looks like this:
ubuntu@ip-172-18-40-84:~/git-server/repos/sandbox-for-jenkinsfiles$ ls -al total 16 drwxrwxr-x 3 ubuntu ubuntu 4096 Sep 19 18:37 . drwxr-xr-x 7 ubuntu ubuntu 4096 Sep 19 14:52 .. drwxrwxr-x 8 ubuntu ubuntu 4096 Sep 19 19:33 .git -rw-rw-r-- 1 ubuntu ubuntu 65 Sep 19 18:37 README.md ubuntu@ip-172-18-40-84:~/git-server/repos/sandbox-for-jenkinsfiles$ git status On branch master nothing to commit, working directory clean ubuntu@ip-172-18-40-84:~/git-server/repos/sandbox-for-jenkinsfiles$
2. Click "Create Pipeline" to go to the Editor.
3. Once inside the editor, without doing anything else, click the "Go to Classic" button:
4. A 404 page is shown. We were trying to get to http://172.18.40.95:8080/job/pipeline-editor:
