If you committed your work to Jenkins, you may have noticed the Jenkins build broke somewhere. We fixed most of it; we fixed our Gulp build after all. However, some issues remain. The build project fails because of some SonarQube issues. You can do three things, fix your code (you would have to remove some alert() and console.log() statements), disable the rules in SonarQube, or configure your Jenkins project, so it will not fail because of SonarQube. That last option is the quickest; simply remove the Quality Gates post-build action. In production code, we would not use alert() and console.log(), but for now, I do not find that a problem.
With the build project running again, we should publish the extra reports we are generating for our Node.js tests. We have an extra Cobertura report, so the XML report pattern should now be test/coverage/cobertura/*.xml,coverage/*.xml...
