Organization-level defaults for new project branch name and New Code period

SonarQube Cloud
1

I’m trying to configure organization-level default settings so that any new project automatically created in SonarCloud starts with the correct configuration.

We have a monorepo where projects/modules can be created dynamically by the scanner. Because of that, we would like to define defaults at the organization level rather than having to configure every new project individually after it has already been created.

Specifically, we want newly created projects to:

Use main as the default branch instead of master.
Use a 30-day New Code definition instead of previous_version.

I tried configuring these settings through the API at the organization level, but they appear to be unsupported.

  • Steps to reproduce:
  1. POST api/settings/set with organization=<org> and key=sonar.projectCreation.mainBranchName, value=main
  2. Same call with key=sonar.leak.period.type, value=days
  3. Same call with key=sonar.leak.period, value=30
  4. All three return the “can’t be set at organization level” error
  5. As a result, every new project auto-created by the scanner is born with master as its default branch (so subsequent main analyses land on a non-default branch and the dashboard shows “not analyzed” until manually fixed) and previous_version as its New Code definition (which never resets, since our CI pipeline never sets sonar.projectVersion)
  • Potential workaround:
    Currently fixing each new project manually after creation via api/project_branches/rename (to main) and api/settings/set scoped to the individual component (for New Code = 30 days). This works per-project but requires a manual step (or a pre-scan provisioning call from CI) every time a new module is added to the monorepo. Requesting whether org-level defaults for these two settings are planned, since SonarQube Server supports them as global defaults today.
2

Hey @natanoelk, welcome to the Community!

Regarding the new code definition, you can set it org-wide in the UI: your org > Administration > New code. If you’re interested in the API behind it, you can check the browser’s dev tools to see the API request: PATCH https://api.sonarcloud.io/organizations/organizations/<your_org> with payload {"name":"<org>,"defaultLeakPeriod":"30","defaultLeakPeriodType":"days"}. But this can just be done in the UI anyways.

For the default main branch name, it cannot be configured: new unbound projects created by analysis default to master. The recommended approach, where possible, is to bind/provision the project through the DevOps integration so SonarQube Cloud can use the repository’s default branch (main). We are aware of this gap and are tracking it internally.