In most development processes there are effectively two types of branches, used for two different purposes: long-lived branches and short-lived branches. The in-product tutorial will indicate where you configure the parameters for your specific case. Where you make this configuration depends on the language you are analyzing and the build tools you are using. For a non-integrated environment you must, additionally, manually set the analysis parameters.
Set up your build script so that, in addition to building on each push to the main branch, a build is also triggered on each push to branch-1Īt this point, you would be done if you were using an integrated CI. Set up your project as described in the in-product tutorial (this sets up main branch analysis). First of all, you would follow the same steps as for the integrated CI: Let's say you want to set up analysis for a branch called branch-1. In this case, you need to manually configure these parameters. Setup with a non-integrated build environmentĪ non-integrated build environment is any build environment (cloud-based CI, local, etc) for which SonarCloud does not provide integration and therefore cannot automatically determine the sonar.branch.* analysis parameters. See Setup with non-integrated CI, below, for details.Īdditionally, in some special cases, even with an integrated CI, you may need to manually set the parameter. In a non-integrated CI, these parameters must be set manually as part of the configuration of branch analysis. This data is sent up to SonarCloud alongside the analysis results and allows SonarCloud to display the results correctly. : The name of the target branch of the branch that was analyzed. : The name of the branch that was analyzed. 
Internally, when the SonarScanner performs a branch analysis in an integrated CI, it automatically sets two analysis parameters: Similarly, whenever you push a commit to any branch matching the pattern branch-*, the analysis will also run and the result will appear on SonarCloud on the page for that branch.
Now, whenever you push a commit to the main branch, the analysis will run and the results will appear on SonarCloud on the main branch page of your project.
It is good practice to check it into all branches, including the main branch, in identical form. You should make sure that this newly altered build.yml file is checked-in to all the branch-* branches. branch-* # The other branches to be analyzed
0 kommentar(er)
