1 Answer
- Newest
- Most votes
- Most comments
0
Your SonarQube instance needs to be accessible from the pipeline environment. Basically you need have your sonar.login and sonar.host.url need to be fed into your pipeline. Here’s a dead simple buildspec.yaml that will run a Maven build and scan, then push results to a SQ instance:
env:
variables:
SONAR_LOGIN: "SONARQUBE_AUTHTOKEN"
SONAR_HOST: "SONARQUBE_URL"
#good to use parameter-store
phases:
build:
commands:
- mvn test123
post_build:
commands:
- mvn sonar:sonar -Dsonar.login=$SONAR_LOGIN -Dsonar.host.url=$SONAR_HOST
This was like completed few years back for one of my client. Also you can explore SonarCloud as well if possible. Checkout below documentation. https://aws.amazon.com/blogs/devops/integrating-sonarcloud-with-aws-codepipeline-using-aws-codebuild/
answered a year ago
Relevant content
- asked 4 months ago
- asked a year ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
Thanks Shashank, I am exploring sonarcloud integration with our aws codepipeline now.
The given doc about buildspec.yaml about maven build, can i have gradle buildspec.yaml.