No branches seen in project
Article ID: 191636
Updated On:
Products
CA Harvest Software Change Manager
CA Harvest Software Change Manager - OpenMake Meister
Issue/Introduction
In our development state, we only have check out/in for concurrent development.
In this instance, only one developer seems to be accessing the code.
In the Eclipse plugin, the developer is using optimistic checkout.
When we look at the version history, it just shows all trunk versions, no branch versions.
How can this be? Is it something to do with the Eclipse interface??
In this instance, only one developer seems to be accessing the code.
In the Eclipse plugin, the developer is using optimistic checkout.
When we look at the version history, it just shows all trunk versions, no branch versions.
How can this be? Is it something to do with the Eclipse interface??
Environment
Release : 13.0.3 and higher
Component : CA HARVEST SCM CORE FUNCTIONALITY/PROCESS AUTOMATION
Resolution
When looking at your checkin process, we find that you must have the “Branch” option checked:
And your context in Eclipse must not have the “Trunk” checkbox checked next to your checkin process:
You need both of those two settings set correctly to be able to Commit to Repository in the Eclipse Plugin and get branch versions – even of existing items. The check-in from regular Explorer View in Workbench doesn’t work this way. It will create a new branch version of an existing item even without that box checked, but both the Eclipse Workspace and Workbench’s Workarea work this way.
(Remember, if you change your Eclipse context you need to do it at the highest folder level for the project and check the “Reset all files to inherit the project-level package” checkbox so that the change filters down.)
And your context in Eclipse must not have the “Trunk” checkbox checked next to your checkin process:
You need both of those two settings set correctly to be able to Commit to Repository in the Eclipse Plugin and get branch versions – even of existing items. The check-in from regular Explorer View in Workbench doesn’t work this way. It will create a new branch version of an existing item even without that box checked, but both the Eclipse Workspace and Workbench’s Workarea work this way.
(Remember, if you change your Eclipse context you need to do it at the highest folder level for the project and check the “Reset all files to inherit the project-level package” checkbox so that the change filters down.)
Feedback
Yes
No
Powered by
