We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When specifying basePlugins list, if I do not provide configuration-as-code-support it complains that required plugin is missing.
basePlugins
configuration-as-code-support
This plugin has been marked as deprecated -> https://plugins.jenkins.io/configuration-as-code-support/
The text was updated successfully, but these errors were encountered:
probably it is marked deprecated as it was proposed and accepted to be part of std component of jenkins? https://github.com/jenkinsci/jep/tree/master/jep/201
Sorry, something went wrong.
Required tasks:
Developer guide is located here
#291 Don't install configuration-as-code-support plugin by default
42ed7db
Fixed in https://github.com/jenkinsci/kubernetes-operator/releases/tag/v0.4.0
jenkinsci#291 Don't install configuration-as-code-support plugin by d…
c39d1cc
…efault
tomaszsek
No branches or pull requests
When specifying
basePlugins
list, if I do not provideconfiguration-as-code-support
it complains that required plugin is missing.This plugin has been marked as deprecated -> https://plugins.jenkins.io/configuration-as-code-support/
The text was updated successfully, but these errors were encountered: