Mistake #32: treating deployment as a manual handoff. A build service turns committed database code into a tested dacpac package before deployment proceeds. section 7.6.2
A build service typically:
- Starts after a pull request or source-control change triggers the pipeline. section 7.6.2
- Runs unit tests to check that the code has not broken existing behavior. section 7.6.2
- Creates a dacpac containing the database object definitions for later deployment. section 7.6.2
A safer release path
A developer commits database changes and raises a pull request. GitHub Actions, Azure DevOps, or Jenkins runs the tests and produces the dacpac. After merging to trunk, deployment services promote that package through development, integration testing, UAT or staging, and production, with environment-specific human gates. section 7.6.2
Figure 7.9 CI/CD process
Use the CI/CD process diagram to follow how build services connect source control, testing, packaging, deployment services, and environments. section 7.6.2
