Skip to content
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

Config file provider plugin fails tests with Jenkins 2.415 #2274

Closed
MarkEWaite opened this issue Jul 22, 2023 · 2 comments
Closed

Config file provider plugin fails tests with Jenkins 2.415 #2274

MarkEWaite opened this issue Jul 22, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@MarkEWaite
Copy link
Contributor

MarkEWaite commented Jul 22, 2023

Jenkins and plugins versions report

Environment
Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

Red Hat Enterprise Linux 8

Reproduction steps

  1. Build and test config file provider plugin with Jenkins 2.414 and confirm it passes
  2. Build and test config file provider plugin with Jenkins 2.415 and confirm 4 tests fail

Expected Results

Config file provider plugin tests need to be adapted to the improvements in Jenkins 2.415 delete dialogs so that they pass the tests with both 2.414 and 2.415.

Actual Results

Config file provider tests fail with 2.415 and pass with 2.414.

https://github.com/jenkinsci/bom/runs/15255225821 lists the specific failures.

Anything else?

jenkinsci/jenkins#7938 (comment) has more details

@MarkEWaite MarkEWaite added the bug Something isn't working label Jul 22, 2023
@mawinter69
Copy link

should be fixed with jenkinsci/config-file-provider-plugin#286

@MarkEWaite
Copy link
Contributor Author

Fixed in config file provider plugin release https://github.com/jenkinsci/config-file-provider-plugin/releases/tag/952.va_544a_6234b_46

MarkEWaite added a commit to MarkEWaite/bom that referenced this issue Jul 22, 2023
MarkEWaite added a commit that referenced this issue Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants