search

devonfw / ide

Tool to automate setup and update of development environment (esp. for Java projects).
Apache License 2.0
35 stars 101 forks source link

SonarQube and Jenkins do not start out of the box #1082

Open mdriesse opened 1 year ago

mdriesse commented 1 year ago

Expected behavior

As a new user, I want sonarqube and jenkins to start out of the box so that I can use both tools.

Actual behavior

With default settings sonarqube en jenkins do not start out of the box.

Steps to reproduce (bug) / Use Case of feature request (enhancement)

  1. Run a clean install
  2. Run devon sonar start --> crash
  3. Run devon jenkins start --> crash

Comments/Hints:

With default setting OpenJDK version 19.0.2_7 is installed. Sonarqube en jenkins do not support this version and require version 17. I recon decoupling the JDK version of the workspace and the tooling would resolve the issue.

Workaround

Add the following line to the file $DEVON_IDE_HOME\settings\devon.properties: JAVA_VERSION=17.0.5_8

Affected version:

2023.03.003

hohwille commented 1 year ago

@mdriesse thanks for your feedback and this issue. We will have a look and find a solution...

hohwille commented 1 year ago

I have merged PR https://github.com/devonfw/ide-settings/pull/28 that implements #1026 so there is already a workaround that will not even require as new software release. If you setup your devonfw-ide from scratch or delete the software/java folder and rerun devon sonar or devon jenkins the error shall be fixed.

However, we will design a clean solution that will work on the long run. My idea is to activate the shared software repo by default once we find a way to keep all software installations pristine or exclude them from symlinking. Then we could add a simple function to run a specific Java version (e.g. 17.* what means the latest version starting with 17.) and this way commandlets like jenkins or sonar could easily be changed to fix this problem properly.

BTW: Java once claimed to be downward compatible so if that would be true these crashes did not happen and there would be no problem at all.

hohwille commented 1 year ago

Already vscode and intellij have been implemented such that plugins are installed separately from the IDE software product itself. We need to find a way to archive this for eclipse and then can finally cleanly solve the above described suggestion.

hohwille commented 1 year ago

was auto-closed by PR but still not fixed. Hence, reopening.