1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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/
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- Réponse acceptéedemandé il y a 2 ans
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
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.