You have got to be kidding me! If the product is promising a tutorial, the least it can do is say “This is the tutorial, now we’ll walk you through creating a new project.” The product doesn’t say that. The “two minute quick install” doesn’t say that.
This is like promising to teach someone how to ski, taking them to the top of the hill, and then saying “OK, now ski.”
Personally I already got around this and have started analyzing some existing Gradle/Java projects. But it’s a huge barrier to any potential customer who wants to try out SonarQube.
You’re right, “embedded tutorial” isn’t the right language for this and it wasn’t clear in the Get Started in Two Minutes guide. A documentation fix is in and will come out with the next version of SQ. Now about those skiing lessons…
Thanks, Mike, appreciate the response (and the upcoming fix).
I’ve noticed a few other documentation “oopses” along the way… but overall our experimentation with SonarQube is going well (and I’ve learned a few things about Java ‘volatile’ along the way from the very useful SonarQube reports).
What is the best way to report what seem like documentation issues?