-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Remove BlueOcean from all of our controllers #4400
Comments
as per jenkins-infra/helpdesk#4400 remove all blueocean plugins
as per jenkins-infra/helpdesk#4400 remove all blueocean plugins
BlueOcean have been removed successfully from infra.ci - jenkins-infra/docker-jenkins-infraci@7ff83a1 on release https://github.com/jenkins-infra/docker-jenkins-infraci/releases/tag/2.2.0-2.486 published and used online with jenkins-infra/kubernetes-management#5922 missed |
the plugin is not installed on weekly.ci - https://github.com/jenkins-infra/docker-jenkins-weeklyci/blob/main/plugins.txt |
the plugins are not installed on LTS docker image : https://github.com/jenkins-infra/docker-jenkins-lts/blob/main/plugins.txt |
as per jenkins-infra/helpdesk#4400 removing the puppet installation of the plugin blueocean on the jenkins controller ci.jenkins.io
as per jenkins-infra/helpdesk#4400 removing the puppet installation of the plugin blueocean on the jenkins controller trusted.ci.jenkins.io
the plugins are not installed on cert.ci.jio https://github.com/jenkins-infra/jenkins-infra/blob/db830e53f4e4b561f4b9bb33d65ea1a51544c700/hieradata/clients/controller.cert.ci.jenkins.io.yaml#L268-L292 |
the plugin is installed on ci.jenkins.io through puppet (making sure it's installed), here is the PR removing it: jenkins-infra/jenkins-infra#3749 (after we will need a manual uninstallation of it through the UI) |
the plugin is installed on trusted.ci.jenkins.io through puppet (making sure it's installed), here is the PR removing it: jenkins-infra/jenkins-infra#3750 (after we will need a manual uninstallation of it through the UI) |
as per jenkins-infra/helpdesk#4400 removing the puppet installation of the plugin blueocean on the jenkins controller ci.jenkins.io
…est (#3750) as per jenkins-infra/helpdesk#4400 removing the puppet installation of the plugin blueocean on the jenkins controller trusted.ci.jenkins.io
uninstallation from trusted.ci and ci.jenkins.io postpone to Thursday to not collide with today release. |
ci.jenkins.io and trusted.ci.jenkins.io have been proceed, no more blueocean on them (including |
ALL DONE, thanks for your services |
Service(s)
cert.ci.jenkins.io, ci.jenkins.io, infra.ci.jenkins.io, release.ci.jenkins.io, trusted.ci.jenkins.io, weekly.ci.jenkins.io
Summary
Following #2833, enough time has passed and we haven't used BlueOcean at all in the past months: the Graph viewer is good enough for our usage now!
Thanks @timja @NotMyFault @uhafner and many other for the work put into this plugin
As such, I propose we remove BlueOcean plugins from all of our controllers:
Note: we might have to reconfigure the default views and to clean up plugins manually on some controllers
plugin list to remove:
blueocean
blueocean-autofavorite:1.2.5
blueocean-bitbucket-pipeline
blueocean-commons
blueocean-config
blueocean-core-js
blueocean-dashboard
blueocean-display-url:2.4.3
blueocean-events
blueocean-git-pipeline
blueocean-github-pipeline
blueocean-i18n
blueocean-jira
blueocean-jwt
blueocean-personalization
blueocean-pipeline-api-impl
blueocean-pipeline-editor
blueocean-pipeline-scm-api
blueocean-rest
blueocean-rest-impl
blueocean-web
jenkins-design-language
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: