We've previously seen examples of the plugin causing SonarQube to fail to start due to runtime dependency conflicts. It has been fixed but it's worrying that this is something our unit tests failed to detect.
Travis should allow us to spin up a Docker container with a base version of SonarQube and install the current version of the plugin to make sure it starts up correctly. The process is not complicated but a little time-consuming if done manually.
An example Dockerfile used in a simple 8.4.1 startup test
FROM sonarqube:8.4.1-community
COPY sonar-aemrules-plugin-1.2.jar $SONARQUBE_HOME/extensions/plugins/sonar-aemrules-plugin-1.2.jar
COPY sonar-findbugs-plugin-3.11.0.jar $SONARQUBE_HOME/extensions/plugins/sonar-findbugs-plugin-3.11.0.jar
followed by building and running an image should do the trick.
We've previously seen examples of the plugin causing SonarQube to fail to start due to runtime dependency conflicts. It has been fixed but it's worrying that this is something our unit tests failed to detect.
Travis should allow us to spin up a Docker container with a base version of SonarQube and install the current version of the plugin to make sure it starts up correctly. The process is not complicated but a little time-consuming if done manually.
An example Dockerfile used in a simple 8.4.1 startup test
followed by building and running an image should do the trick.