![]() if ] || ] thenĭuring the first analysis, issues (type, severity, status, assignee, change log, comments) are synchronized with the main branch. In the following example, analysis would be limited to branches named main or release/*. For example, you wouldn't want to run analysis on feature branches that won't need analysis until they have pull requests. You need to add a condition to your pipeline script to ensure that only the relevant branches are analyzed. Applies to conditions on new code and overall code.Ī branch is created when the parameter is passed during analysis.The branch quality gate lets you know if your branch is ready to be merged. See the Defining new code documentation for more information, and look at the Clean as You Code strategy to learn how to implement this best practice. This is especially helpful if you are likely to develop and release multiple versions from the branch. ![]() You can set a new code definition for each branch. The new code definition is the only exception to this as it can be set on a branch-by-branch basis. Settings and quality profiles on branchesīranch settings and quality profiles are the same as those set for the main branch, and by design, it's not possible to configure other values. This will put everything back into a consistent state. The solution is to re-analyze the project. ![]() This could lead to an inconsistent state. Impacts on analysis processing: If you change the main branch during a busy load of background tasks, it may impact certain background tasks that process analysis reports.To avoid this, ensure the branch analysis is always pointing to a specific branch. If you change the main branch, you could unintentionally have analyses from the old main branch go to the new branch. In this case, the analysis automatically points to the main branch of the project. Impacts on CI setup: Starting in Developer Edition, it is possible to analyze a branch without passing an explicit branch name ( ).In the second case, changing the project’s main branch does not change the portfolio, as the portfolio is referencing a specific branch. ![]() The recomputation mechanics are the same as for applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |