Integration Manager Workflows & Pull Requests with Git and Mercurial
Integration Manager Workflow
Overview
If you are not familiar yet with the basics of Integration Manager Workflow, we suggest you to read the Version Control Workflows page as a pre-requisite.
Codebeamer is the only product on the market that implements the Integration Manager workflow in a DVCS-agnostic way: it enables using the same methodology for both Git and Mercurial teams.
What repositories are the components of this approach?
Based on the illustration:
• Blessed: Is a server side repository, that stores the official reference version of the source code. This is typically from which code-base products are built or product instances deployed.
• Integration manager: Is the local clone of blessed, used by the team lead, a senior developer or whoever actually integrates changes proposed and sent by the developers.
• Developer public: Repositories are server side forks of blessed. Typically each developer has his own fork.
• Developer private: Repositories are clones of the developer public repositories. They physically exists on the developers work stations. Developers work in this repositories, then push their changes back to developer private: 's and ask the integrator to propagate those to blessed.
Integration Manager Workflow: Demo Video
Watch the following Video to know more.