It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,845
×11,980

question asked: Apr 09 '14, 12:40 p.m.
question was seen: 3,736 times
last updated: Apr 09 '14, 3:18 p.m.

Related questions

Best practices to sync developer workspaces to stream after baseline replacement

0
w h (19●18●24) | asked Apr 09 '14, 12:40 p.m.
edited Apr 09 '14, 12:42 p.m.

We have a New Release stream and Fix Stream which share the same component.  The Fix Stream release ready and has been snapshot / baseline. We would like to do an inplace replace of baseline on the component in the New Release Stream, based on the Fix Stream baseline.

What we can tell, it looks like in every Developer Workspace that is branched off of New Release, each developer will need to replace the component baseline in their workspace as well. 

Is this best practice, or is there something we're missing? In CC UCM we could run a update view and it would update changes down from stream to view.

Thanks!

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Tim Mok (6.6k●3●8) | answered Apr 09 '14, 3:18 p.m.
JAZZ DEVELOPER
Any change in a flow target has to be manually accepted into your repository workspace. This is normal since dynamic views from CC isn't a feature in RTC. This is to prevent a user's sandbox update without his/her knowledge.

Your answer

Register or to post 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.