It's all about the answers!

Ask a question

Question about RTC Baseline History graph in RTC 6.0.2

Karthik Krishnan (8785111158) | asked Oct 06 '16, 9:37 a.m.
edited Oct 06 '16, 12:39 p.m. by David Lafreniere (4.8k7)
After the upgrade of our RTC from 6.0.1 to 6.0.2, I was evaluating the usage of RTC Baseline "History Graph" functionalities.

We have streams where different baselines of each components are consumed.We normally use "Replace" components with specific baselines. 

I can see in the baseline graph the same baselines on different stream but arrow from where it flows is missing.
Why so? See attachment. 

Will this work only for baselines created from RTC 6.0.2 onwards?
Baseline graph

Accepted answer

permanent link
Andrew Niefer (7135) | answered Oct 06 '16, 11:11 a.m.
The flow arrows require information which was not recorded in the server prior to 6.0.2. 

Even in 6.0.2, existing APIs for some operations (accept/deliver) indicate what the source is, but other API for operations like replace do not specify sources.  New API was added to specify the source, but N-1 clients won't call the new API, and even in 6.0.2 clients, not all user actions will have the source available.  For example, replace with latest from stream has a source, but replace with baseline does not.

In particular, build engines should be updated in order for the post-build deliver (which is actually a replace) to report the source of the baseline.

Here is an image showing recent flows for our stream which are the result of our continuous build process:
Recent history

And here is another screenshot of the same graph, just scrolled down earlier in history before the upgrade to 6.0.2:
pre 6.0.2
David Lafreniere selected this answer as the correct answer

One other answer

permanent link
Ralph Schoon (62.3k33643) | answered Oct 06 '16, 10:23 a.m.
edited Oct 06 '16, 10:25 a.m.
If you just replace component baselines, there is no flow. My best guess.

Customize the information shown

By default, this diagram shows how baselines flow between streams and repository workspaces. It also hides certain baseline operation nodes that are less important to many users, such as backup baselines that are created as a side-effect when you replace the baseline in your repository workspace. You can change the default settings to filter out certain information, depending on your needs.

Here are the available filters:

Your answer

Register or to post your answer.