Hi @oleg-nenashev I saw some threads about JDK so I was using JDK8 to run the failed build. I'm also using the latest master from
$ /usr/libexec/java_home -V Matching Java Virtual Machines (1): 1.8.0_252, x86_64: "AdoptOpenJDK 8" /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home $ git show --name-status commit 7ca186c7d82d315d139fb19a05a72dcd2fc66668 (HEAD -> master, origin/master, origin/HEAD) Author: Francisco Javier Fernandez Gonzalez <firstname.lastname@example.org> Date: Mon Apr 6 18:40:58 2020 +0200 [maven-release-plugin] prepare for next development iteration M pom.xml
I ended up modifying
properties/jenkins.level as you suggested and got it working. Thanks!
One more question.
mvn hpi:run also fails on Jenkins repo itself
jenkins master$ mvn hpi:run [INFO] Scanning for projects... [...] [INFO] <<< maven-hpi-plugin:3.13:run (default-cli) < compile @ jenkins-parent <<< [INFO] [INFO] [INFO] --- maven-hpi-plugin:3.13:run (default-cli) @ jenkins-parent --- [INFO] Logging initialized @7148ms to org.eclipse.jetty.util.log.Slf4jLog [...] [ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:3.13:run (default-cli) on project jenkins-parent: The parameters 'minimumJavaVersion' for goal org.jenkins-ci.tools:maven-hpi-plugin:3.13:run are missing or invalid -> [Help 1]
What should I change in this case? Thanks!
I've added a test to
test/src/test/java/hudson/model/ItemGroupMixInTest.java and am trying to run the tests.
mvn test -P light-test fails with this error which doesn't seem related to my changes.
java.lang.RuntimeException: Internal error: Failed to find the "modifiers" field in method setInternalState.
In fact, the same error occurs when the test is run on master branch without any changes. What am I missing? Thank you!
mvn test -P light-teston my Ubuntu 18.04 running AdoptOpenJDK 1.8.0_242 without any issue.
brewinstaller on macOS not setting
JENKINS_HOMEenvvar. It sets the path correctly so the test initiates but as it progresses some parts don't finish. This was seen on both JDK 8 and 11. When
JAVA_HOMEwas set both 8 and 11 succeded
#jenkins-hackhousein IRC? Or would we like to use IRC as a communication channel?
Jenkins version 2.164.2
Folders plugin version 6.9
I'm facing a strange issue. In two folders (out of ~50) some jobs' name and the link changed.
Name should be (from inside
.. » test-frameworks » pre-merge
Link should be
As a result, clicking the name of the job leads to 404. I can get to the job page if I manually fix the URL on the address bar.
Attempting to create a job with the same name fails with
» A job already exists with the name ‘pre-merge’
config.xml's of the affected folders and a non-affected and didn't find any obvious issues.
I've also looked at
config.xml of the affected job but it didn't contain any references to its name. I guess the job name is based on the folder name?
Has anyone seen an issue like this?
Rechecking the tutorial to prepare the environment to contribute (https://www.jenkins.io/doc/developer/tutorial/prepare/) it recommends Eclipse Maven plugin (http://maven.apache.org/plugins/maven-eclipse-plugin/), which was retired. Should we change the recommended approach for Eclipse users?