Revert "Bump configuration-as-code from 1.34 to 1.35 (test harness renamed)"#164
Revert "Bump configuration-as-code from 1.34 to 1.35 (test harness renamed)"#164
Conversation
|
or
|
|
I vote for
|
|
At least starting with the plugins mentioned here, of course. At a rough approximation: |
|
And You should really look into the second option as a provisional measure. |
I work from the bottom you work from the top? |
|
@timja sure |
|
🦆 false postive, all good antisamy-markup-formatter-plugin/pom.xml 🥈 jenkinsci/antisamy-markup-formatter-plugin#17 Taking a break 😓 |
This comment has been minimized.
This comment has been minimized.
|
ecutest-plugin/pom.xml 🥉 jenkinsci/ecutest-plugin#137 |
I guess when those have releases, you will file a PR to revert the reversion plus bumping those versions. |
|
PRs are now open for all plugins in Jesse's list, most builds are passing, need to loop back round to ~4 of them |
|
List of open pull requests: |
|
Continued in #172 |
|
FYI, I did a GitHub search that revealed a few extra: https://github.com/search?q=org%3Ajenkinsci+configuration-as-code+classifier+tests+NOT+test-harness+filename%3Apom&type=Code |
Reverts #161. While this did not produce any test failures, it also caused the majority of plugins to be skipped. Between this and this we see
Easily seen locally, e.g.
⇒
Seems that jenkinsci/configuration-as-code-plugin#917 is incompatible with
plugin-compat-testerusage, as jenkinsci/configuration-as-code-plugin#1215 (comment) warned. You should choose from