diff options
| author | Megan Wilson <84590144+megan-wilson-sonarsource@users.noreply.github.com> | 2022-04-07 10:52:36 -0500 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-04-14 20:03:30 +0000 |
| commit | 2e251c1d86f3627413b44d2c8641e6c92d67bc25 (patch) | |
| tree | 1a96b467374f60a3b798960769fcafacc68b4f10 /server/sonar-docs/src/pages/setup | |
| parent | a7ec93c39c39d487f67e7bbfa0cda4d4999c0bdc (diff) | |
| download | sonarqube-2e251c1d86f3627413b44d2c8641e6c92d67bc25.tar.gz sonarqube-2e251c1d86f3627413b44d2c8641e6c92d67bc25.zip | |
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.
Diffstat (limited to 'server/sonar-docs/src/pages/setup')
| -rw-r--r-- | server/sonar-docs/src/pages/setup/scanner-environment.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/server/sonar-docs/src/pages/setup/scanner-environment.md b/server/sonar-docs/src/pages/setup/scanner-environment.md index c7718955cb9..6caabaf4812 100644 --- a/server/sonar-docs/src/pages/setup/scanner-environment.md +++ b/server/sonar-docs/src/pages/setup/scanner-environment.md @@ -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: ``` |