0 votes
146 views
in Interview Questions by

1 Answer

0 votes
by (2.3k points)
selected by
 
Best answer
Honestly tracks don't do what most of us who are used to SCM systems like git would prefer.  There is no diff / merge capability at this time, so you can create a patch in one branch and then "merge" it into another.  There really isn't a good way to use tracks for concurrent development as they are implemented today.

What they are good for is for creating a patch to production.  Since you can create a track from a snapshot, if you need to create a patch for your production system you can create a track for that patch, fix and test your code, then make a new snapshot for promotion and testing.  Unfortunately if the items you modified have been modified in your "main" branch as part of,say, the next release, then whatever you did in your track will need to be manually duplicated in main.  

If the item you modified as your fix in main are unchanged, you can copy the modified items back to the main track (actually you can do this anyway, but you will over write the other changes done in that track)

Related questions

0 votes
2 answers 1k views
+1 vote
2 answers 1.8k views
0 votes
1 answer 351 views
+1 vote
1 answer 535 views
0 votes
0 answers 72 views
0 votes
1 answer 715 views

589 questions

483 answers

89 comments

1.8k users

Dosvak IBM BPM /BAW Products, Download Evaluation
Process & Performance Tools Process & Performance Tools
Code Analyzer Code Analyzer
UI Toolkit UI Toolkit
Integration Monitoring Integration Monitoring
Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
Created by Dosvak LLC
Our Youtube Channel
...