Using AWS, Docker, Jenkins and SonarQube to improve code quality
Last updated
Last updated
It combines static and dynamic analysis tools and enables quality to be measured continually over time. Everything from minor styling choices, to design errors are inspected and evaluated by SonarQube. This provides users with a rich searchable history of the code to analyze where the code is messing up and determine whether or not it is styling issues, code defeats, code duplication, lack of test coverage, or excessively complex code.
There is much more that can be done with SonarQube, for additional information - https://www.sonarsource.com/products/sonarqube/
I will be installing SonarQube within a Docker container because it is the easiest way to install it. But before that, I need to launch an EC2 Instance.
Creating t2.medium Ubuntu instance
Instance created. Naming convention simple and consistent
Once the instance is ready to go SSH into it so that, then I can install Docker. I have another write up detailing how to ssh into it here - https://app.gitbook.com/o/e400wbcI84apWTnM3t5L/s/tzurpgroDJSMn9AFVmQP/cloud/aws/cloudshell-ssh-in-to-ec2-instances
if the error pops up that private keys are too accessible, it is because you did not chmod 400 or 600