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/
已回答 1 年前
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- 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.