For the past weeks I’ve wrote a series of articles on how to create a continuous integration server which began with the article Tools for a Continuous Integration (CI) server for PHP projects.
You can automate much more than what I’ve shown in this series of articles, specially front-end processes or automated tests and I hope you got to a point where you can investigate and start to tweak the continuous integration process to match your needs.
In the previous article we’ve installed SonarQube and SonarQube Runner. Now that we have the tools, let’s analyse the Laravel 5 project that we’ve created in the second article of “How to set up a Continuous Integration Server for PHP projects”.
This series or articles begun with the article Tools for a Continuous Integration (CI) server for PHP projects and teaches you how to create a continuous integration server from the scratch.
One of the most neglected processes in Software Development is the ability to know how exactly is your project’s health. To do so you need a complex and periodic analysis to ensure your project’s maintenance is sustainable. There are several tools that help you to perform such analysis and among them is SonarQube.
In this article, which is part of the series “How to create a continuous integration server” and began with the article Tools for a Continuous Integration (CI) server, I’ll show you how to install and configure SonarQube and SonarQube Runner.
