Build Configurations for Git Stream

Question

How do people customize their build configurations when using Git and Git-flow? I have several tasks that I want to perform:

• Commit - compilation, start of static code analysis, unit test, package
• Integration Tests - Run Integration Tests
• Deployment for testing - deploying the application in a test environment
• Functional test - run end-to-end functional tests
• Deployment in QA - Manually draw into a QA environment that conducts smoke tests.

With the wizard, create, release function branches. I am curious how people map them into assembly processes.

Answer 1

We currently have

• Ci build
  • The root of the VCS Root has a branch specification that includes development, function / *, release / *, fix / *, and wizard
  • VCS commit trigger for all branches
  • Debug the design of query assembly elements and get assembly results and approve
  • Auto Merge Wizard → Development
• Release Notes
  • Snapshot at CI Build
  • Generates release notes from commits and commits it
• Deployment in Dev Build
  • Snapshot at CI Build
  • Scheduled to deploy twice a day
  • Only a branched branch is deployed
• UAT Build Deployment
  • Manual step
  • Snapshot at CI Build
  • Only release / *, patch / *, or the wizard can be deployed to UAT
• Expand in Prod
  • Manual step
  • Deploy Snapshot for UAT Build
  • Only the master can be deployed here (when the release or hoftix is ​​closed, the master must be deployed to the UAT to test smoke)

Teamcity auto merge does not allow the use of wildcards, so we are working on our own method to synchronize branches.

• master → development, release / *, correction / *
• develop → feature / *

Answer 2

This is my workflow:

Reflective Function (dymitruk.com)

it is adapted from nvie's