-
Notifications
You must be signed in to change notification settings - Fork 52
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 build-failure-analyzer-plugin#181 workaround #3537
Comments
Now that PR-3838 has merged, reverting the excludes for BFA.
it appears the fix doesn't cover jenkinsci#3537. Putting this back in to see if jenkinsci#3539 works ok.
We can't close this one yet. It's still broken. I should have done the 2 issues separately. |
We need to wait for 2.452.x and 2.462.x to both fall off before we can remove the excludes for 181. The first LTS release date (if I did calendar math right) where that happens is June 25, 2025. That means the 2.479.x line will be the oldest line about 4 weeks before, or somewhere around May 28, 2025. |
The test fix from jenkinsci/build-failure-analyzer-plugin#181 could also be backported to the older lines, but casual maintainers are unlikely to do this and it's likely not worth the effort for a fix that doesn't affect production users. Just mentioning this for completeness, as I have done it before for plugins I maintain. |
Once jenkinsci/build-failure-analyzer-plugin#181 is merged, released, and adopted, the workaround added in #3508 should be deleted.
The text was updated successfully, but these errors were encountered: