Flow vs add functionality of components
What is the difference between flowing of components from a repository workspace to a stream and adding a component with the add button functionality in a stream. Is there any information tracked that a component has been flowed to a stream or has been added to a stream?
I ask because of following scenario: (2 Streams, 1 RWS) - Create a new component in RWS - Deliver (flow) the component from RWS to S1 - Add the same component (initial baseline) with the add button to S2 - Remove the component in RWS When setting the flow from RWS to stream 1 and 2 after removing the component from RWS, we get the following result: - Outgoing (-) to S1 (Flowing from RWS to S1) - Incoming (+) from S2 (Flowing from RWS to S2) Why we get an incoming (+) instead of an outgoing (-) in case 2? We are using RTC 5.0.2 ifix10 |
2 answers
Ralph Schoon (63.3k●3●36●46)
| answered Dec 10 '15, 5:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
As far as I am aware there is no information kept about the flow of changes or the component addition or removal. There might be temporary
In your scenario 1, you have the component on the stream, and you don't have it on the RWS after the deletion. The workspace knows that component was deleted from it. Hence the system tells you that and asks you if you want to deliver the component deletion, which is basically just going to remove the component. In your scenario 2, you don't have the component on the RWS, but the component is on the stream the first time the difference is computed. So there is an incoming component addition. I don't know if you can get different results if you change the order of events. Comments Hello Ralph,
The last operation you did on the RWS was a remove component. So your repository workspace has changed with respect to S3 and the change is removal of a component. So you have the option of removing it from the stream as well, and not an incoming addition. It is fairly logical that it is implemented that way. If someone else adds a component to a stream and you flow with it you see it incomoing. If you have less than the stream it is incoming. If you have more than the stream it is outgoing.
Hello Ralph,
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 12 '15, 8:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Each stream has an event history, which records the events that have modified that stream, such as the addition and removal of a component (baseline), including when that event took place. When a component is in the stream, but not in the workspace, my understanding is that if the component has been deleted from the workspace and the date of the removal of the component from the workspace is later than the date of the addition of the component to the stream, then it is treated as an outgoing deletion ... otherwise it is treated as an incoming addition.
Comments
...my understanding is that if the component has been deleted from the workspace and the date of the removal of the component from the workspace is later than the date of the addition of the component to the stream, then it is treated as an outgoing deletion ... otherwise it is treated as an incoming addition. This is also my understanding and the reason why I'm asking, because in my scenario I first add/flow the components to the stream and at the end I remove the component out of my rws. Example with timestamps: [09:00] Create a new component in RWS [09:01] Deliver (flow) the component from RWS to S1 [09:02] Add the same component (initial baseline) with the add button to S2 [09:03] Deliver (flow) the component from RWS to S3 [09:10] Remove the component in RWS The expected behaviour according to your answer will be, that I get in all three cases an outgoing deletion. I don't understand why I'm getting in one case an incoming addition. Can you please check this behaviour with an empty workspace and a new component according to the steps above. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.