forked from VirtusLab/jenkins-operator
-
Notifications
You must be signed in to change notification settings - Fork 236
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
WARN: install-plugins.sh is deprecated #739
Labels
bug
Something isn't working
Comments
brokenpip3
added a commit
to brokenpip3/kubernetes-operator
that referenced
this issue
Dec 10, 2022
* the fix was original attempted here: jenkinsci#764 but was not working correctly due to 2-3 additional changes which needed to be done * removed the openshift check because the env is not mention anywhere and also the new jenkins-plugin-cli does not a specific command for openshift. Finally this does not make any sense in general, the only problem in ocp will be the user id that will be mapped to a random uid but that's another story. The command to install the plugins should remain the same across different k8s flavours.
prryb
pushed a commit
that referenced
this issue
Jan 12, 2023
…t the newest jenkins lts version (#784) * fix(seed): fix #742, workaround #698 Original fix proposal: #742 (comment) * fix(install-plugin.sh): fix #758, #739 * the fix was original attempted here: #764 but was not working correctly due to 2-3 additional changes which needed to be done * removed the openshift check because the env is not mention anywhere and also the new jenkins-plugin-cli does not a specific command for openshift. Finally this does not make any sense in general, the only problem in ocp will be the user id that will be mapped to a random uid but that's another story. The command to install the plugins should remain the same across different k8s flavours. * fix(doc/test): fix /usr/bin/tini in any doc and validation * fix(jenkins): remove AdminWhitelistRule to avoid jvm stack trace, see: https://www.jenkins.io/doc/book/security/controller-isolation/jep-235/#api-compatibility * fix(seed): fix seed img built on a previous jvm, fix #761 * fix(plugin): update the base plugin to work with the newest version of jenkins:lts * fix(run): fix #778 * fix(backup): add a trap to remove the tmp dir if the tar fail, also fix: #770 * test(chart): update chart values for testing, will revert before merge * fix(configmap): leftover * fix(tests): fix seed job test * fix(e2e) * fix(e2e): helm * fix(operator): update the temporary img to reflect latests changes * Fix Helm e2e tests * add trap in case of unwanted exit and make shellcheck happy * chore(plugin): update git ver to 5.0.0 * fix(backup): always force delete the backup directory * chore(operator): update the temporary img to reflect latest changes * chore(jenkins): upgrade jenkins latest lts
Hi @samuelbernardolip this has been solved with this commit: 60b8ee5 please try this version and let me know :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
WARN: install-plugins.sh is deprecated, please switch to jenkins-plugin-cli
To Reproduce
Deploy a jenkins instance with operator snapshot virtuslab/jenkins-operator:29c5b1e and current master CRD resource.
Additional information
Kubernetes version:
Jenkins Operator version: 29c5b1e
Add error logs about the problem here (operator logs and Kubernetes events).
Debug message in container logs:
WARN: install-plugins.sh is deprecated, please switch to jenkins-plugin-cli
The text was updated successfully, but these errors were encountered: