David Karr <[email protected]> writes: [...]
> This started happening in one project, among several, on the first build > after midnight on 1/26. The previous build, just before midnight, didn't > fail with this. Jenkins displays all the git commit ids that it checked > out for the builds, and they are identical for both builds. That seems to > indicate that there were no code changes between the successful build and > the failed build. IIRC, I had very similar problem when build started using Java 12 instead of Java 8. --8<---------------cut here---------------start------------->8--- mvn --show-version Apache Maven 3.6.0 Maven home: /usr/share/maven Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.19.0-2-amd64", arch: "amd64", family: "unix" --8<---------------cut here---------------end--------------->8--- I found it very helpful to run CI jobs with 'mvn --show-version' to spot changes in JDK/Maven version being used. -- Mykola Libre/Free Java Software Engineer https://manandbytes.gitlab.io/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
