-
Notifications
You must be signed in to change notification settings - Fork 9
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
io.jenkins.tools.pluginmodernizer.cli.CommandLineITCase fails locally #476
Comments
Interesting it should not be dependant of the environment. Also on WSL2. Can you check the logs of Thanks |
I also tested on Ubuntu 22.04 (arm64):
I got the same error:
|
Are you using 2 different local repository ? The interesting part is
Which mean the previously build of core is not resolved from the local repository According to logs, the local repo used by plugin modernizer is
Maybe a custom settings ? |
Let me know if resolved by #485 I added also more log to debug such issue |
It still fails on a machine with a freshly cloned repo.
|
For the
So something must be hardcoded somewhere, making it work only on |
As for my WSL2/Debian machine, it is now solved. |
Interesting, Perhaps the maven binary used for integration tests. It's added as artifact on the pom.xml of the CLI module. Probably some maven config is necessary to download the correct architecture. During test the JDK is also downloaded on the cache. So that we don't depends on existing installation of sdkman during integration tests. |
I think I could do something about that, depending on the architecture we're running on. |
Plugin Modernizer version
plugin modernizer 999999-SNAPSHOT (2024-12-18T09:41:06Z)
What Operating System are you using
Debian on WSL2
Reproduction steps
mvn install
Expected Results
No error.
The text was updated successfully, but these errors were encountered: