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 plugin management #769
Remove plugin management #769
Conversation
I guess update sites is automatically moved to unclassified block? Which is fine, perhaps you could verify? 🤔 |
I can't see any test case or demo for that feature. Since you use it, what's the config you normally use, maybe you want to add a test and demo for it 😉? Happy enough to add later on if you can send an example though |
@timja rats 🙍♂️ |
@Casz sorry, but I don't understand your comment :P is it ok to merge in your opinion? |
He asked me to validate it and I would like to validate it quickly 😄 I'll merge once I can confirm that update site is possible to manage 😄 Or add a test even. |
} | ||
|
||
private UpdateCenter configureUpdateSites(Mapping map, Jenkins jenkins, ConfigurationContext context) throws ConfiguratorException { | ||
final CNode sites = map.get("sites"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update site require some more code it seems 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah damn, happy to make it work if you push a test 😉
2be0d75
to
6a59308
Compare
plugin/src/main/java/io/jenkins/plugins/casc/core/UpdateSiteConfigurator.java
Show resolved
Hide resolved
plugin/src/test/resources/io/jenkins/plugins/casc/plugins/ProxyConfigTest.yml
Outdated
Show resolved
Hide resolved
Thanks @Casz LGTM |
and +1 from me, I don't see a problem with updateCenter under jenkins root element |
afaik all custom configurators have been put under the jenkins model EDIT: not correct ignore me, seems fine |
…onfiguration-as-code-plugin into feature/remove-plugin-management
I would like to fix up the proxy configuration too! This way we don't depreciate all features that were in plugin management but just move them from fancy management to configuration part. |
I'm happy to do that part won't take long, unless you're already doing it? |
@timja I welcome you, I am on a train to work 😄 |
same |
Not quite sure what to put in the describe function, the test is currently failing and the export fails:
will poke at it later today unless you know what's missing |
@ndeloof or @Casz either of you got time to have a quick look and see what's wrong with the configurator?
the Just need to run the ProxyConfiguratorTest |
@Casz I made the proxy config work, although I couldn't get the export to work, I was getting stackoverflow errors... Probably haven't implemented the configurator quite right, but given how the ProxyConfiguration code is structured in core it's not the easiest to make work... I'll see if I have time to send a PR to core for improving it there |
bbe9c1e
to
9b5ca8e
Compare
…onfiguration-as-code-plugin into feature/remove-plugin-management
I'll give this PR a look to see if I can fix export, if not. I will go ahead and cut a release either way 😄 Does that sound like a deal @ewelinawilkosz ? |
a default describe covers most scenarios for a configurator, if more complex cases are needed you would override the describe method
@@ -156,6 +157,15 @@ default Class getImplementedAPI() { | |||
* Only export attributes which are <b>not</b> set to default value. | |||
*/ | |||
@CheckForNull | |||
CNode describe(T instance, ConfigurationContext context) throws Exception; | |||
default CNode describe(T instance, ConfigurationContext context) throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ndeloof do you have anything against a default describe? This can be used for basic cases.
MavenConfigurator
would need a custom but Jenkins
, AdminWhitelistRuleConfigurator
, UpdateCenterConfigurator
, UpdateSiteConfigurator
seems to settle for default case
this good to go @Casz? |
I think so, but I would love a comment from the original author whether a default describe is good or bad 🗡️ ping @ndeloof 😅 |
🤷♂️ |
See [JENKINS-53767] Offer plugin management tooling
|
Here is our checklist for contributors. No hard requirement here, just a reminder
Please describe what you did
Remove plugin feature
Link to issue you're working on if there's a relevant one
Related to: allowRestart flag added #766
Did you provide a test-case to demonstrate feature actually works / issue is fixed ?
Removed lots of them 😆
Please also consider adding a line to CHANGELOG.md