-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link Bitbucket to classic Jenkins UI instead of Blue Ocean as an option #630
Comments
That system property has some problems, see JENKINS-69006 and jenkins-infra/helpdesk#2833 |
Can you uninstall Blue Ocean entirely? I did that, but perhaps you are using some plugins that depend on it. |
Based on the description, it does not apply to us, since we do not use GitHub and also all users are logged in and we do not need exemptions from this rule. After a quick check everything seems normal for us. I will report back in a week. As for uninstalling, we considered this, but we want to keep working on improving support for it. We just need a dynamic switch. |
JENKINS-69006 is not really specific to GitHub. |
Sorry, I don't know what role 'display/redirect' plays in all of Jenkins. For us it works fine without that suffix. |
The JENKINS-69006 issue is that setting the system property causes the URLs to be generated without the display/redirect suffix, and those URLs can then be included in email messages or other notifications that are saved by external systems. If you ever change your mind and remove the system property, then the URLs that were generated and saved while the system property was active will not start redirecting to Blue Ocean again, even though newly generated URLs may do so. That may be all right for your purposes. |
In the meantime, JENKINS-69006 has been fixed, and there is talk about removing Blue Ocean from the Jenkins base distribution. |
What feature do you want to see added?
Classic UI can still be in many terms more functional than Blue Ocean. An option to link Bitbucket to the classic UI instead of Blue Ocean would help here. Blue Ocean is unusable in our environment due to various missing features related to Jenkins customization and plugin support.
EDIT: Just found out that I can run
System.setProperty('jenkins.displayurl.provider', 'org.jenkinsci.plugins.displayurlapi.ClassicDisplayURLProvider')
In the script console and that does what I need. I guess it is resolved, but feels like something that should have been configurable in Blue Ocean in the first place. Maybe someone can shed more light on this?
Upstream changes
No response
The text was updated successfully, but these errors were encountered: