-
Notifications
You must be signed in to change notification settings - Fork 718
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
[JENKINS-51469] Add Essentials configuration to CasC tests #216
Conversation
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.
I would just split it to "MetricsPluginTest" and "SystemMessage" test. The provided test does not really verify that metrics are loaded correctly tho
@oleg-nenashev that is right, the test does not check everything that could be, I filed it as-is for now since it does fail locally for me though. Failing the exact same way as in essentials tests currently on the |
I bisected the issue:
gentle ping @ndeloof @ewelinawilkosz thanks! |
just from the top of my head - a lot of configurators that were under jenkins root element are moved to unclassified now, maybe you need to fix your yaml? |
@ewelinawilkosz possibly. Checking the docs. That rings some bell somewhere, but I didn't follow closely your changes TBH indeed. |
the docs... I should review the dosc and make sure everything is aligned. didn't do that before :( |
@ewelinawilkosz we can adjust the yaml if need be. I've just no idea as to what to do actually. cc @ndeloof |
sure, |
indeed, as part of the "export" feature development, as I can't compare current Jenkins instance state with a reference state (one can't build two |
Also enrich tests heavily in the go.
@ndeloof @ewelinawilkosz adapted the PR to the new format. I believe, once the PR build is green, it would be valuable to merge this to more easily track compatibility with what we use on Essentials side. Thanks! |
Failure here because of FindBugs failing on |
Merci Nicolas. |
This PR is based off
configuration-as-code-0.5-alpha
on purpose.On my machine,
mvn clean verify
is successful.But if I update (i.e. merge or rebase) on latest
master
it fails.It fails with the following error: