Hi,
THANK YOU VERY MUCH! 
I really mean it!
Is there some documentation which variables you are using for this, so people using GitLab, but not GitLab-CI, can get the same level of integration?
Anyways, congratulation on the release!
Regards, Tobias
Hi Tobias,
Is this what you’re looking for: https://docs.sonarqube.org/latest/analysis/gitlab-cicd/ ?
(Note that it’s part of the embedded documentation, so once you upgrade it’ll be at your fingertips. 
)
Ann
Hi Ann,
thank you for this new feature and congratulations. 
What about gitlab release supported ?
Is it available for GitLab Community Edition On premise ?
Thank you in advance.
Best regards
Stéphane
Hi,
I already found that part of the documentation. That is clearly doing something “magic” to detect the current “context” (project, branch, commit ID, merge request, etc.) - I just want to know what those variables are, so I can use the SonarQube-GitLab integration from other CI solutions (Jenkins, TeamCity, etc.)
TIA, Tobias
Hi Tobias,
Sorry to be dense, but I’m confused. You want to know the names of the GitLab envvars so you can use them in other CI environments? If I’m reading that right, I’m pretty sure Jenkins is going to have differently named envvars than GitLab does…?
Ann