Getting snapshot as incoming change
2 answers
Comments
Right Martin, its not Snapshot, its base line but i don't know why this baseline is coming as incoming change.
If you have two Stream, Stream A and Stream B, and in Stream A you have 3 Change Sets.
If you have a flow target from Stream A to Stream B you will see that three Change Sets as outgoning.
If you now create a snapshot (and thereby a baseline) you will see your baseline as outgoing change (instead of the three changes sets). Therefore a deliver of the baselines, deliver also the containing change sets.
You can also expand the baseline in the pending changes view to see the containing change sets that are not yet in your flow target.
If you create new Change Sets, after the creation of the snapshot, you will still see the baselines, and the change sets you have created after the snapshot.
Baselines are basically configurations of element versions of a component that belong together. They flow like changes. You deliver them after you create them on a repository workspace and you accept them if someone created and delivered them to a stream.
You can flow from one stream to another if, and only if, there are no conflicts. The main usage is to promote a new state f a stream to another (e.g. from TEST to PROD). Typically there is only one direction of flow and thus conflicts can not happen.
If you have conflicts, you have to resolve them using a repository workspace.
The typical flow is to have a workspace W1 based on Stream1. They are in sync. Then you change the flow target to Stream2. You get differences between W1 and Stream2. You accept changes from Stream2 into W1 and merge conflicts if needed. Once done, you can deliver the changes to Stream2. You change the flow target back to Stream1 and can deliver the merged changes back to that. At this point the streams are in sync.
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Nov 13 '14, 6:43 a.m.RTC version?
Ashok Sharma
Nov 13 '14, 8:13 a.m.its 4.0.3