Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleProject unicity under a portfolio

Projects, applications and sub-portfolios can only appear once in any given hierarchy in order to avoid magnifying their impacts on aggregated ratings. The portfolio configuration interface has some logic to prevent obvious duplications (e.g. manually adding the same project), however in case of more subtle duplications (e.g. due to regex, or other bulk definition), then the calculation of that portfolio will fail with a helpful error message.

Calculation

...

(warning) From SonarQube 7.1, Portfolios and Applications are automatically re-calculated immediately after any changes to their component parts. Attempting to force calculation in SonarQube >=7.1 using the command described below will fail with an error. However, re-calculation is not automatically triggered after a definition/structure change. For that, you can either wait for a new project analysis to organically trigger recalculation, or use the Recompute button found in the configuration page. Note that you can still use the Administration > Projects > Background Tasks page to see when automatic recalculation of your Portfolio or Application was triggered.

...

Calculation must be triggered manually each time a Portfolio structure is modified. Portfolios should also be recomputed on a regular basis to keep them up to date with the most recent project quality snapshots. Portfolio are computed with the SonarQube Scanner.

...