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?
FWIW even Visual Studio Code provides basic software development features. I often have to use it on my work laptop which has serious RAM limitations
Have used it only for Angular projects. Can't see it handling dependencies and imports as good as other IDES. Will try my way with IntelliJ community, hopefully I won't miss anything :)