@Alexandre_Holzhey, yes! We need firt-analysis for “release-v” branches. However I have doubts if we will be effective.
My flow, with details:
Concept branch:
- Branchs develop, master and release-v* are considered long living.
- Branchs feature-v* and hotfix are considered short living.
Step 1: My dev team create a branch feature(short living), after create a PR to merge branch develop. In moment the merge the build pipeline is executed and run code analisys sonar is make. After release pipeline create my application in enviroment develop in my cloud.
Step 2: If ok deployed in enviroment develop, my dev team create a branch release based on branch develop (already analyzed). The build pipeline are executed in branch release-v*.(In my vision in that model, the coverage will fail, why branch release is based in branch develop, no changes). After release pipeline executed deploy in enviroments QA, Homol (in homol we have the gate SonarCloud in post-deployment) and PRD.
Step 3: If ok deployed in all stages, is realized o merge to branch master. (just for your knowledge of my total flow)
- Additional informations:
We have a script to is executed in firt step build pipelines named “SetupSonar.ps1”, this script create project, add permissions to users, getting tokens in Keyvaults Azure, authenticate in SonarCloud, Set PR integration and set new code period to 30 days, Set Long living branches pattern, after change general in format of analisys in code, my issues starting.
I tried to describe my complete flow in many details to make it easier for you to understand and see how you can help, as I am not seeing any way out of this case.
Regards,