New Code reference branch by default

[anon67236913]

Welcome

as there is no property (yet) you may use the rest api for project provisioning, see

Sonar property for reference branch

Hi, no need to create a branch via api, as it is automatically created via sonar.branch.name property during the analysis. We use it like that, i.e. A generic Jenkins pipeline for Maven builds implemented as shared library and driven by a yaml config file. The pipeline checks if project already exists using api/projects/search , if not it is created. https://<yoursonar>/api/projects/create?project=com.foo:foobar&name=foobar Normally project is created automatically, it’s only because of …

and

Sonarqube 8.4.1 branch analysis, definition of new ?!

Think i’ve found a working hack. api/projects/search?projects to check if project already exists api/projects/create if it doesn’t exist api/new_code_periods/set?project=$projectkey&type=REFERENCE_BRANCH&value=master api/new_code_periods/set?project=$projectkey&branch=master&type=PREVIOUS_VERSION run Sonarqube analysis Thought 3. would not be possible if project is newly created in 2. ,but it is. Should also be almost safe for parallel builds and scans of the same project !? A…

Gilbert