Browse Source

SONAR-16283 Add redirect for new page Scanner Environment

updated scanner-environment to put back the links for JDK and Tool Environment Plugin for Jenkins.
tags/9.5.0.56709
Megan Wilson 2 years ago
parent
commit
2e251c1d86
1 changed files with 2 additions and 2 deletions
  1. 2
    2
      server/sonar-docs/src/pages/setup/scanner-environment.md

+ 2
- 2
server/sonar-docs/src/pages/setup/scanner-environment.md View File

@@ -78,7 +78,7 @@ If your build is not compatible with Java 11 or 17, then you can override the `J

### Jenkins

You can define a new JDK in **Manage Jenkins > Global Tool Configuration**, if you have the JDK Tool Plugin installed.
You can define a new JDK in **Manage Jenkins > Global Tool Configuration**, if you have the [JDK Tool Plugin](https://plugins.jenkins.io/jdk-tool/) installed.


#### Declarative Pipelines
@@ -149,7 +149,7 @@ All the other steps in the job will use the globally configured JDK.
Jenkins does not offer functionality to switch JDKs when using a **Freestyle project** or **Maven project** configuration.
To build your project using Java 8, you have to manually set the `JAVA_HOME` variable to Java 11 or 17 when running the analysis.

To do this use the **Tool Environment Plugin**. This plugin lets expose the location of the JDK you added under **Manage Jenkins > Global Tool Configuration**.
To do this use the [Tool Environment Plugin](https://plugins.jenkins.io/toolenv/). This plugin lets expose the location of the JDK you added under **Manage Jenkins > Global Tool Configuration**.
The location of the JDK can then be used to set the `JAVA_HOME` variable in a post step command, like this:

```

Loading…
Cancel
Save