Hey there.
I don’t think there’s a compelling reason to separate your build/scan into two jobs – for analysing Java, you want to have the build done right before the scan (and in the same context, with all the output generated by the build available). Even better, this way the build only has to run once.
With regard to this error:
This has come up before and it is probably easiest for now to just remove sonar.projectKey from your pom.xml and, if it’s something that does match your Maven project’s <group id>:<artifact id> format, specify it as an option to your Maven command (-Dsonar.projectKey=com.projectname:services)
And, I’ve taken the point to investigate this a little further (something is wrong here with the SonarQube tutorial and multi-module maven projects).