Error with execution of SonarExecute Scan from Jenkins piper library

[CargillRamya]

Please note: I had set up a jenkins pipeline job and all configurations for sonar server are done in the backend. Also, config.yml is set up with values

steps: sonarExecuteScan: sonarTokenCredentialsId: 'sonarqube_integ' proxy: '...' sonarServerUrl: '...' dockerEnvVars: http_proxy: "..." https_proxy: "..."

But I get the below error:

• ./piper sonarExecuteScan info sonarExecuteScan - Using stageName 'SonarQube Analysis' from env variable info sonarExecuteScan - Project config: '.pipeline/config.yml' info sonarExecuteScan - [DEBUG] GET https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.6.2.2472-linux.zip info sonarExecuteScan - [ERR] GET https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.6.2.2472-linux.zip request failed: Get "https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.6.2.2472-linux.zip": dial tcp: lookup binaries.sonarsource.com on 10.47.133.68:53: no such host info sonarExecuteScan - [DEBUG] GET https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.6.2.2472-linux.zip: retrying in 1s (15 left)

[sarunkumar1990]

Also we have already installed sonarqube plugin and have set SONAR_USER_HOME within our environment variables section in JenkinsFile but piper does not look at this variable and always tries to download the CLI.

Is there a possibility to check if this variable is already set and use the CLI which is already installed instead of downloading each time?

[github-actions[bot]]

Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add @SAP/jenkins-library-team to your comment.

[github-actions[bot]]

Issue got stale and no further activity happened. It has automatically been closed. Please re-open in case you still consider it relevant.