Azure DevOps Build Agent + Local SonarQube | Java, SSL Certificates and Node Setup

Published 26/02/2026

Description

Learn how to prepare a Windows build machine for Azure DevOps so it can run SonarQube analysis against a local, SSL-secured SonarQube server. SonarSource says self-hosted agents need a supported Java runtime for SonarQube analysis, and its TLS guidance explains that scanners may also need operating system trust and Java truststore configuration when the server uses self-signed or internal CA certificates. In this video, I walk through the exact setup needed on a self-hosted build agent: installing Java, importing internal certificates, and fixing Node.js trust issues so the Azure DevOps SonarQube integration can connect cleanly to a local server. SonarSource community guidance specifically calls out that self-signed certificate problems can affect both Node.js and Java separately, and one common Node-side fix is NODE_EXTRA_CA_CERTS. 0:00 - Introduction 0:12 - Description 0:42 - Java 2:58 - Certificate 4:49 - Conclusion What you’ll learn: Why Java matters on the build machine. SonarQube’s Azure DevOps integration documentation says that if you self-host build agents, you must install at least the minimum Java version supported by your SonarQube version. How to trust an internal or self-signed certificate. SonarSource documents adding the certificate to the operating system trust store and, for Java-based scanner flows, to the Java truststore or a custom truststore when needed. Why Node.js can still fail after Java is fixed. SonarSource community threads show that NodeJS requests used by Azure DevOps tasks may not automatically trust the same internal CA, which is why NODE_EXTRA_CA_CERTS is often part of the solution. Why this is especially relevant for self-hosted agents. SonarQube’s Azure DevOps extension documentation explicitly distinguishes self-hosted and on-premise scenarios and notes minimum agent requirements for SonarQube tasks. This video is useful for DevOps engineers and sysadmins running Azure DevOps with an on-prem or locally hos