Closed InfoSec812 closed 6 years ago
This was flakey for me when running CI initially; sonar wouldn't come up or would start coming up and then the new image that gets built would kill it and it would go into a funny state based on the imagechange trigger - we should watch this for flakeyness in the future; but i'll merge for now!
By building and deploying SonarQube BEFORE the Nexus server (and it's associated delay), we are more likely to have SonarQube running before Jenkins starts and this the autoconfiguration of Sonar in Jenkins will be successful on initial deployment.