Previous: Preproduction/Staging, Up: Git Workflow Environments [Contents]
In both the Gitflow and the TBD models, ‘master’ branch represents the live environment where the software is deployed and made available to end-users or customers as a stable version. However, the rate of pushes to this branch varies in every workflow, thus, the CI pipeline’s tasks need to be optimized depending on this condition.
While in Gitflow the ‘master’ is protected and new commits can only be merged to it through the ‘release-*’ and/or ‘hotfix-*’ branches, the TBD approach lets developers commit directly to the production branch, assuming all responsibility in case something does not go well and/or conflicts with another component. For this reason, it is vital to have a CI pipeline which works quickly and efficiently; while with the other workflow, this aspect is more permissive and there is not as much risk of the appearance of bad commits that cause a serious problem to the production environment or stable version.