From 842fd06539714b5f4d005fb5023cbe24973ff6b1 Mon Sep 17 00:00:00 2001 From: Toni Kangas Date: Sat, 5 Jul 2025 20:01:00 +0300 Subject: [PATCH] Update host IP admonition title --- docs/tutorials/jenkins/sonarqube-jenkins/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/jenkins/sonarqube-jenkins/README.md b/docs/tutorials/jenkins/sonarqube-jenkins/README.md index 240f58c..c26b82f 100644 --- a/docs/tutorials/jenkins/sonarqube-jenkins/README.md +++ b/docs/tutorials/jenkins/sonarqube-jenkins/README.md @@ -47,7 +47,7 @@ If this succeeds, you are ready to move this analysis into Jenkins. First, install SonarQube Scanner plugin to your Jenkins instance through [Manage Jenkins > Manage plugins](http://localhost:8080/pluginManager/available) menu. Configure SonarQube instance to SonarQube servers section of the [Manage Jenkins > Configure System](http://localhost:8080/configure) menu: Use `http://sonarqube:9000` as the server URL and create a secret text credential for the access token you stored earlier. -??? example "Alternatives for using `sonarqube` hostname" +??? example "Use hosts IP instead of `sonarqube` hostname" The `sonarqube` domain name is by default only available for containers attached to the same network. Thus the the connection from Jenkins container works with the `sonarqube` hostname, but opening these links from the browser will fail.