Some time ago we have created a branch from our original application. The original application is live. We have merged the trunk project to the branch and we will soon go live with this new/extended application. When we want to create a branch from this branch we receive a message that this is not supported.
Since the original application will be obsolete anyway, we would like to 'upgrade' our current branch to trunk. Is this possible and if so, how?
We are currently using 2018.3.
Solved
Changing a Branch-project to Trunk-project
+12- Superhero
- 136 replies
Best answer by Anne Buit
Hi Hugo,
That does complicate things a bit.
You can run the following query on the 2018.3 Software Factory database to change the branch into a project that can be used as a trunk.
View originalThat does complicate things a bit.
You can run the following query on the 2018.3 Software Factory database to change the branch into a project that can be used as a trunk.
code:
update project
set branch_project = 0,
trunk_project_id = null,
trunk_base_project_vrs_id = null
where project_id = 'NAME_OF_BRANCH_PROJECT'
This topic has been closed for comments
+5Hi Hugo,
This is technically possible. But before we go down this road, isn't it easier to merge the branch back to the trunk and continue from the updated trunk?
This is technically possible. But before we go down this road, isn't it easier to merge the branch back to the trunk and continue from the updated trunk?
+12- Superhero
- 136 replies
Hi Anne,
Yes, that would be a good (and simple) solution. I suppose we could decide all conflicts in favour of the branch. Would in that case the new trunk be 100% equal to the branch?
Yes, that would be a good (and simple) solution. I suppose we could decide all conflicts in favour of the branch. Would in that case the new trunk be 100% equal to the branch?
+5Hi Hugo,
Yes, this should be the case, if no changes have been done to the trunk since you merged the trunk to the branch.
Yes, this should be the case, if no changes have been done to the trunk since you merged the trunk to the branch.
+12- Superhero
- 136 replies
Hi Anne,
We did change a few things in the trunk which we also changed in the branch. But in the mean time we upgraded the branch to 2018.3 where the trunk is still 2018.2. The projects are in 2 different SF's...we did not plan on merging them again.
We did change a few things in the trunk which we also changed in the branch. But in the mean time we upgraded the branch to 2018.3 where the trunk is still 2018.2. The projects are in 2 different SF's...we did not plan on merging them again.
+5Hi Hugo,
That does complicate things a bit.
You can run the following query on the 2018.3 Software Factory database to change the branch into a project that can be used as a trunk.
That does complicate things a bit.
You can run the following query on the 2018.3 Software Factory database to change the branch into a project that can be used as a trunk.
code:
update project
set branch_project = 0,
trunk_project_id = null,
trunk_base_project_vrs_id = null
where project_id = 'NAME_OF_BRANCH_PROJECT'
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.