-
Improvement
-
Resolution: Fixed
-
Critical
-
Jenkins 2.7.4, Blue Ocean 1.0.0-b07
-
-
frank, tethys, iapetus, 1.0
Do not start this work if the new headers are not on master
Scope
- Add the "exit to classic" link to both the header of application and to the run modal
App header
Run header
Original request
If I navigate to a Pipeline, deep within a GitHub Organization Folder, it's impossible to quickly get to the "classic" UI with my current browsing context.
If I want to get from a detail page for a pull request run, I need to open a new window, click the folder, click the repository, click pull requests, click the appropriate pull request job, then click the build number.
It would be nicer if there was a little link in the header of the detail page which allowed me to "view in classic" or something like that. That way I could easily go from this detail view to this classic page without wanting to flip my desk.
- is duplicated by
-
JENKINS-42035 Blue Ocean - Button to go between classic and blue ocean view.
-
- Closed
-
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-38751] run results and main header to provide an "escape" link to get back to a classic view of a Pipeline/job
Hans Schulz
added a comment - If this button would be available, we could already switch to Blueocean as default.
Its already great for viewing build logs and results (essential when builds use parallel), but there are situations where it is not sufficient yet. In these situations its a pain needing to navigate through all folders to the exact run when I just want to view the normal UI.
Hans Schulz
added a comment - If this button would be available, we could already switch to Blueocean as default.
Its already great for viewing build logs and results (essential when builds use parallel), but there are situations where it is not sufficient yet. In these situations its a pain needing to navigate through all folders to the exact run when I just want to view the normal UI. 
Julien Pivotto
added a comment - I do not agree. DO is far form being acceptable as default. It misses tons of features (build parameters? folders? slave executors?) and is really (already) too heavy even for moderns laptops and browsers.
Julien Pivotto
added a comment - I do not agree. DO is far form being acceptable as default. It misses tons of features (build parameters? folders? slave executors?) and is really (already) too heavy even for moderns laptops and browsers. Hans Schulz
added a comment - Sorry, I need to clarify, with "we" I meant the team and build environment im working in, not the Jenkins community as a whole.
Still, having this button would allow more users, which do not rely heavily on features not yet implemented in Blue Ocean, to switch the default to it and use the classic UI in situations where needed.
Hans Schulz
added a comment - Sorry, I need to clarify, with "we" I meant the team and build environment im working in, not the Jenkins community as a whole.
Still, having this button would allow more users, which do not rely heavily on features not yet implemented in Blue Ocean, to switch the default to it and use the classic UI in situations where needed. Julien Pivotto
added a comment - Yes, for that I agree.
My proposal is to have a "Close Blue Ocean" button, at the same place as the "Open Blue Ocean" button. That would make sense.