1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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/
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
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.