How do I find source stream of the changeset
Hi,
Is there any way, by which , we can find out the source stream on which , the changeset was first delivered onto ?
We are using multiple streams , so changset does move from one stream to another.
So, how do I find the original source of the change or first stream in which it was delivered into ?
RTC version being used V4.0.6
|
2 answers
A similar question was asked here - https://jazz.net/forum/questions/142782/how-to-determine-the-workspacestream-and-component-combination-a-change-set-was-delivered-to-using-oslc-rest-plain-java
You can find which streams/workspaces contain a particular changeset but there doesn't seem to be such a thing as 'source stream' of a changeset.
Comments 1
Ralph Schoon
commented May 18 '15, 2:41 p.m.
| edited May 19 '15, 6:30 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes. A Stream can contain data. But which one contains what might change due to rebasing etc.
Lily Wang
commented May 19 '15, 9:51 p.m.
I agreed this is not possible in RTC 4.0.6. But it may be possible since RTC 5.0.1.
In RTC 5.0.1, a new "Date Added" column is available in the History view which shows the date that a change set is added to the stream/workspace history. (See https://jazz.net/downloads/rational-team-concert/releases/5.0.1?p=news#AddByInfoInHistoryView)
With this feature, you can use "Locate Change Set" to find all streams that contain the change set. Then open the stream's history and compare the "Date Added" of the change set.
The stream which has the earliest "Date Added" is the first stream the change set is delivered to.
Ralph Schoon
commented May 20 '15, 10:43 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Nevertheless, I think that this elevates "Being Added to a Stream" to a level that it should not have, especially because the stream could be already deleted, set to another baseline etc. You can see if a change set is in a specific stream, workspace now, or is (forever) in a certain baseline. You can tell who added it there. That is pretty much all you can.
|
The question of origin of source would still be needed, especially when you have to troubleshoot or RCA a change , which broke everything.
It also gives exact picture of changes being done in each release / sprint stream, which is not merged from previous or other streams.
So, while Locate change-sets and date added would certainly help, but it requires lot of manual efforts to do that, when you have 7-8 streams or work-spaces.
Comments
Donna Thomas
commented May 27 '15, 9:04 a.m.
Also, workspaces are just as volatile as streams are. They are deleted more so than streams in our environment. Besides, you can change the flow target of the workspace to different streams, so it makes it very difficult to trace the change through a stream. The date and locate change set help, but it really should show the stream as well. The stream has much more impact than Mr. Schoon is giving it credit. In trying to locate a change set, it would be very useful to indicate which stream.
|
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.
Comments
You are not alone in wanting to see this answer. :)
Why do you want to know the first stream a change set is delivered to?
Would you be able to describe your situation a little more? It will be nice to know which stream is the build stream and how other streams are flowing to it. Are the changes flowing automatically or manually?