Bear in mind that SonarQube will have access to your code (and have a copy for analysis purposes), so it's important that you protect it. Next step is to generate a project token, which will be used for identification. Definitely not recommended for production projects.Ĭlick on that Create new project and put some names there We could set up external DB or map the storage volume, but for the purpose of quick start we'll stick with the embedded DB. The embedded database will not scale, it will not support upgrading to newer versions of SonarQube, and there is no support for migrating your data out of it into a different database engine. While logging in, you may notice this warning:Įmbedded database should be used for evaluation purposes only If you keep refreshing like I did, you'll see this at some point
If you can't open the page immediately, wait a bit, don't panic. Log in to localhost:9000 with System Administrator credentials (login=admin, password=admin). We wan't to see SonarQube up and running. I did a brief check and saw that SonarQube use ElasticSearch underneath and this flag prevents some checks that we don't care about at the moment. And, you always can use a Google to check it on your own. Obviously you have to put it, since it's in bare minimum quick start documentation. 1-communityįor now I don't know what this SONAR_ES_BOOTSTRAP_CHECKS_DISABLE flag is, but it's not important to understand for now. Start the server by running: $ docker run -d -name sonarqube -e SONAR_ES_BOOTSTRAP_CHECKS_DISABLE= true -p 9000 : 9000 sonarqube: 8.5. Find the Community Edition Docker image on Docker Hub (we did this already) There will be a link that points to this piece of documentation You might want to read everything there but I already did that for you. OK, image is there, now what? Like with every docker image, check the documentation on Docker Hub, here in our case. Check it out, newer versions may be available.
#Getting started java lwjgl download#
Where did I get this? There's a docker pull command on the SonarQube download page, ready to be copied. No external installations or things like that docker pull sonarqube: 8. Let's keep it simple, we'll run a SonarQube container and after we are done playing with that, we can wipe it off from our system like it never existed. In case you're not familiar with it, you may want to check Docker Images - Intro for beginners that I wrote. There are some tools that can show you that, and today I'm writing about SonarQube.īut, since I like the approach with minimum steps required, I'll write just as much as I think it's necessary for the beginning. How do we know if the code we write is good enough? Error free? Not vulnerable? Not smelly?