WorkArea Synchronizer view

[Jarus Bosman]

Hi,

My Development and Production states share the same view (as per the CA Harvest supplied Production Model template). When I make changes to an item in Development (on the branch) and promote it through the lifecycle all the way to production (merging in  the Merge state), and then synchronize, it shows my changed items in the Synchronizer view as "Incoming changes". I suspect this is because they are now trunk versions whereas my workspace file is still seen as the branch version (I see this in the synchronizer view on the different versions that are displayed). Is this the right way of using the WorkArea? Do I have to right-click all my changed items and select "Update from repository" every time I make changes to remove these "Incoming changes"?

Regards,

Jarus

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------

[Balakrishna Shantamurthy]

HI Jarus,

Thanks for the question here.

We are of the below understanding ,Please see the steps below.

1.WorkArea was created from Development view, package pack1 of the project. At this point all versions of the development view and work area are in sync.

2.Now you have created a branch version on the Development view using same package,pack1 ,promoted this package ,pack1 to the production view

3.Now you are executing the synchronize on the work areas and see the branch versions as INCOMING VERSIONS.

4.This is expected behavior only as the branch version changes are implemented at a later point than the versions created in work area using the same package.

The context package used in the work area is still the same when it was initially created.

NOTE: If the BRANCH changes are included ,using a different package ,then from work area incoming change will not be seen.

If the changes(Branch or Trunk) in the Development state are done at a later point then it needs to be fetched into work area using Update from repository only.

Workarea is generally used /created from the Development view for the changes to be done on the local file system and in a stand alone manner to be able to perform operations/trial changes and then commit only when you are completed the changes to be able to commit to the repository.

More information on work areas can be viewed from here.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/harvest-scm/14-5/using/work-in-the-workareas.html#concept.dita_a6bd35ac92289082d4b274f4334871c056de6208_WorkAreas.

Please let us know if you need further information.

Regards,

Balakrishna

[Jarus Bosman]

Hi Balakrishna,

May I just reiterate again as per my initial post, that my Development state does not have its own view. It shares the Production view with the Production state, because that is how the supplied CA Harvest Production Model Lifecycle template defines it, and that is the model we decided to use.

Having said that - The explanation you provided makes sense. Does that mean I should tell my users that they have to perform an "Update from repository" action in their Development state WorkArea after all their changes were merged to trunk and promoted to the Production state?

Kind regards,

Jarus

------------------------------
Jarus Bosman
Senior Software Developer
State Information Technology Agency
South Africa
------------------------------

[Balakrishna Shantamurthy]

HI Jarus,

Thanks for the details.

As the workarea is created from Development state and it has a shared view with the production.

To be able to not miss out the  changes included in the production state ,it is always better to fetch the latest versions from the repository and continue working.

This may also reduce the possibility of merging the changes frequently.

Please ,let us know if you have further questions here!!

Regards,

Balakrishna