Provider "jar" not found about plugin-installation-manager-tool

[gounthar]

I tried to build the current main branch in my Docker container and got:

247.9 [INFO] Running io.jenkins.tools.pluginmanager.impl.ChecksumTest
247.9 [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s -- in io.jenkins.tools.pluginmanager.impl.ChecksumTest
247.9 [INFO] Running io.jenkins.tools.pluginmanager.config.LogOutputTest
247.9 [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s -- in io.jenkins.tools.pluginmanager.config.LogOutputTest
248.2 [INFO]
248.2 [INFO] Results:
248.2 [INFO]
248.2 [ERROR] Failures:
248.2 [ERROR]   CacheManagerTest.cacheManagerWithNonReadableJsonFileForKey:159
248.2 Expecting actual:
248.2   ""
248.2 to start with:
248.2   "Cache ignored file the-cache-key.json because it cannot be read.
248.2 java.nio.file.AccessDeniedException:"
248.2
248.2 [ERROR]   CacheManagerTest.cacheReturnsNullWhenCachedFileCannotBeRead:148
248.2 expected: null
248.2  but was: {}
248.2 [ERROR] Errors:
248.2 [ERROR]   PluginManagerTest.startNoDirectoryNoPluginDirTest:143 » ProviderNotFound Provider "jar" not found
248.2 [INFO]
248.2 [ERROR] Tests run: 151, Failures: 2, Errors: 1, Skipped: 3
248.2 [INFO]
248.2 [INFO] ------------------------------------------------------------------------
248.2 [INFO] Reactor Summary for plugin-management-parent-pom 2.13.1-SNAPSHOT:
248.2 [INFO]
248.2 [INFO] plugin-management-parent-pom ....................... SUCCESS [02:21 min]
248.2 [INFO] plugin-management-library .......................... FAILURE [01:33 min]
248.2 [INFO] plugin-management-cli .............................. SKIPPED
248.2 [INFO] ------------------------------------------------------------------------
248.2 [INFO] BUILD FAILURE

[gounthar]

It builds correctly on the same machine without Docker for JDK 17 and 21. 🤔

[gounthar]

Thanks to the assistance of @MarkEWaite, we've identified and resolved the issue with the Docker image that was causing problems with the Jenkins WAR file.

Root Cause

The problem stemmed from an incorrect ENV variable declaration in the Dockerfile. Specifically:

• I mistakenly used {} in the ENV variable declaration.
• This resulted in an empty WAR file, rendering Jenkins unusable.

Solution

The issue was resolved by correcting the ENV declaration in the Dockerfile:

• Removed the {} from the ENV variable declaration.
• After this correction, everything began functioning properly.

Lessons Learned

1. Pay close attention to syntax in Dockerfile ENV declarations.
2. Avoid using {} in ENV variables within Dockerfiles.

Next Steps

1. We can consider closing this issue.
2. Alternatively, we could keep it open to improve the error message:
   • Current message: "jar: Provider not found"
   • While this gave us some clues, a more descriptive error message could be helpful.

Reflection

Although it's unlikely that others will encounter this specific error, improving error messages can always benefit users and troubleshooting processes.

Acknowledgment

I take responsibility for this oversight. Thank you to everyone involved in helping diagnose and resolve this issue.