-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add local sonar analysis #32
add local sonar analysis #32
Conversation
The CI failure happened because this project had fewer tests than JHipster Lite. Therefore, Sonar isn't ready when the tests finish and try to connect to it. I could simulate this failure on my machine by executing the following script: docker stop sonar
docker rm sonar
docker rmi sonarqube:10.5.1-community
docker compose -f src/main/docker/sonar.yml up -d
./mvnw clean verify -Dsonar.qualitygate.wait=true sonar:sonar I am looking for an elegant solution instead of creating a script to retry or sleep to check if Sonar is up before running the tests. |
I gave up and added a sleeper 😅😎 |
Adding a sleep is a simple solution, no need to go further, as it's enough for our use |
Thanks for the feedback 😀 |
See #24