Staged Team Commit

Context

Unusable continuous integration, too many commiters and higher need for integration within a team.

In large sized projects if the continuous integration is unusable because of lot of commiters, a lot of waste is incurred. This waste can be limited by creating smaller team specific continuous integration flowing into the main integration.

Description

A set of commiters (generally a team) define their own source control (or a branch) off which they work. There is a continuous integration system which facilitates, integration of code within the group and create output which can be used for downstream activities. On a periodic basis the local code is merged with trunk (main branch).

Use of distributed version control system is recommended over centralized ones as they are designed for handling frequent branching and merging of code.

Limitations

Integration of code is limited within the team and across different teams the integration is not continuous. This can lead to all the issues caused by not doing continuous integration like integration hell, bad merge etc.

Increases the testing effort as merge verification is required.