Missing Dependency in PluginAutomaticTestBuilder?

[sghill]

Hi,

I'm not quite sure where to report this issue, but this seems like a reasonable place to start. The answer may well end up being somewhere else, however - I also faced this issue when updating plugins on my most recent Jenkins deployment. Declaring the commons-text-api as a top-level dependency worked there, which points to this being more than a test harness issue.

I've been updating some plugins from baseline Jenkins 2.375.4 to 2.387.3 and getting several failures from InjectedTest.testPluginActive that look like this:

[ERROR] InjectedTest.testPluginActive -- Time elapsed: 0.003 s <<< FAILURE!
java.lang.AssertionError: While testing build-name-setter, plugin-util-api failed to start
        at org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests.testPluginActive(PluginAutomaticTestBuilder.java:98)
...
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.io.IOException: Failed to load: Plugin Utilities API Plugin (plugin-util-api 3.3.0)
 - Plugin is missing: commons-text-api (1.10.0-36.vc008c8fcda_7b_)
 - Plugin is missing: commons-lang3-api (3.12.0-36.vd97de6465d5b_)

plugin-util-api is not a dependency of the project. In looking at the dependencies of recent releases of plugin-util-api, I did not see anything to suggest this dependency was just dropped either. Here are a few examples where running mvn clean verify will reproduce the problem:

• sghill-rewrite/build-name-setter-plugin@37109a9
• sghill-rewrite/description-setter-plugin@318c117
• sghill-rewrite/matrix-project-plugin@45b8215
• sghill-rewrite/plugin-usage-plugin@70c7f3c
• sghill-rewrite/project-stats-plugin@5de167e

In one case I fixed the test by adding a test-scoped dependency, but a more centralized fix would be better.
jenkinsci/naginator-plugin@85c11e2

[jonesbusy]

Was initially reported on BOM: jenkinsci/bom#2484 but the culprit is checks-api-plugin

[MarkEWaite]

Was initially reported on BOM: jenkinsci/bom#2484 but the culprit is checks-api-plugin

We hope to remove the requirement for that workaround in the next plugin BOM release, expected within the next day or two.

[MarkEWaite]

Closing this issue because the root cause issue is tracked in the checks-api plugin as:

• Dependencies of flattened POM of latest release do not match MANIFEST.MF checks-api-plugin#233

Thanks for reporting the issue @sghill !