ADO Service Connections
An Excel document with the list of service connections for Platform Operations and CNP.
Create a SonarCloud Service Connection with PlatOps Github account
Get Platform Operations Github account credentials
The credentials stored in the Azure Key Vault rpe-prod
. See the table below for the secrets.
Credential | Secret |
---|---|
Username | github-bot-owner-username |
Password | github-bot-owner-password |
Recovery codes | github-bot-owner-recovery-codes |
The recovery codes are used as an alternative to the 2FA. Currently the Username is set as hmcts-platform-operations
Generate a user token for the Github account
- Open a browser in incognito mode
- Go to sonarcloud and choose
Github
login option - Sign in and then go to Security tab
- Provide a meaningful token name and click on Generate Token. As of writing this doc there are two generated tokens
Jenkins
andpat-sonarcloud-platops-github
. The latter one is used in this SonarCloud service connection - Take a note of generated token as it will be used later
- Create a new secret in the Azure Key Vault
rpe-prod
with the namepat-sonarcloud-platops-github
and the value as the generated token
Create a SonarCloud service connection in Azure DevOps
Go to the Azure DevOps project where you want to create the service connection. e.g. Shared Services. go to Project settings > Service connections > New service connection > SonarCloud.
Paste the token generated in the previous step in the field SonarCloud Token
and click on Verify and Save
.
You can also update the SonarCloud Token
by launching the existing SonarCloud service connection in Edit
mode.
This page was last reviewed on 21 February 2024.
It needs to be reviewed again on 21 February 2025
by the page owner platops-build-notices
.
This page was set to be reviewed before 21 February 2025
by the page owner platops-build-notices.
This might mean the content is out of date.