|
|
|
|
|
|
|
|
|
|
- Overview
- How to manage branches
Branches allow you to simultaneously manage several versions of the same application. Common case: You have released a version of your application, and are already working on the next version. However, you also want to deploy bug fixes from the new version to the release version, and thus create and distribute intermediate versions. Another example: You can also use branches to manage versions specific to certain users. Each branch corresponds to a client version. As soon as the base project (common trunk) is modified, all you have to do is apply the modifications into each one of the branches. Branches allow you to effortlessly deploy software update. The risk of errors due to "manual reporting" disappears. The comfort increases, the security increases, the hurdles to availability of bug corrections disappear... Remarks: - The branch modifications are bi-directional. Changes in the main project can be applied to the branch, or vice versa. The project that is modified is always the open project.
- Starting with version 2024, the SCM administrator allows you to create branches in directories that do not contain any projects. For more details, see SCM administrator: Managing branches.
 New in version 2025Starting with version 2025, branch and directory deletion has been optimized. To take advantage of this optimization, use the latest version of the SCM repository. For more details, see SCM: Repository versions. Note: This feature is only available from version 2025 Update 1.
To manage the branches, the SCM proposes: Note: With project portfolios, you can create a branch on a set of projects in a single operation. For more details, see Project portfolio.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|