-
Notifications
You must be signed in to change notification settings - Fork 72
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
Plugin is not available on jenkins #164
Comments
https://www.jenkins.io/security/advisory/2022-08-23/#SECURITY-2448 any alternative solutions? |
You can download the older version of plugin and manually installed on jenkins |
2.3.1 from other place doesnt' work, it's dont like apiv1 in deployment.yaml |
An updated version is available here: Note: none of the security advisories have been addressed. |
Thanks, i will give it a try! |
I've got a problem, tabs at source java code doesn't supported ?
String 9 is |
Config file setting should be **/*.yaml |
Are you able to download the old version ? |
Did you find the Solution |
Unfortunately, after digging into it, the work needed to fix that is more than just updating the deps version. Some Kubernetes schemas got deprecated and removed from the java client. Now to update the version (which will get rid of that CVE) one need to update all the referenced wrappers. And that's not that easy. |
One guy fixed it, but it's not support ingresses, so i use kubectl apply -f and then i think i get do all the stuf this way, without any jenkins plugins..) |
The plugin is up for adoption. If your organization needs this plugin, then you should persuade your organization to let you adopt the plugin, fix the security issue, modernize the plugin, and release a new version with the fix. |
Describe your use-case which is not covered by existing documentation.
Hi
Could you please suggest the alternate method for which the plugin is used now for deployment ?
Regards: Hamza
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
No response
The text was updated successfully, but these errors were encountered: