Pull/Push to different Parent Branches
This is what I'd like to do: I want to expose a main trunk that provides a "tip" with the most recent and successfully compiled content. However, I wish to protect the main trunk from dispensing problematic content to developers by first running a compile and associated regression tests before the changed content is committed to the main trunk.
The feature mentioned above could be implemented by creating a parallel trunk (another branch) that accepts developer changes (pushes). Once the changes have been verified, the content would always be pushed (never merged) from the parallel trunk into the main one.
To determine the feasibility of the above, a simple simulation was constructed using a bzr shared repository. The shared repository was created with the following branches: a main trunk, a parallel trunk, and a developer's branch. I used bzr explorer and set the pull parent to the main trunk and the push parent to the parallel trunk. Afterwards, the contents of the main branch were pulled to the developer's branch. The developer's branch was then updated, committed, and then pushed to the parallel branch. Finally, the parallel branch was pushed to the main trunk. All worked as expected for this simple case, however, I'm just wondering if there's some reason to be concerned about this configuration. Also, is there known and better implementation for the feature outlined above.
Thanks!
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Bazaar Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- John A Meinel
- Solved:
- Last query:
- Last reply: