scm set flowtarget --flow-components mycomp does not work
RTC 4.0.5.
The way I understand the RTC 4 documentation, scm set flowtarget can be used to modify the target to flow only select components instead of all components of a stream. I am running scm create workspace -r rtc_uat -e my_compB_wksp Workspace (1055) "my_compB_wksp" successfully created scm add flowtarget my_compB_wksp myStream -r rtc_uat The flow targets were added. scm add component -r rtc_uat -s myStream my_compB_wksp compB Following components successfully added: (1056) "compB" scm list flowtargets -r rtc_uat my_compB_wksp -j [ { "current": true, "default": true, "name": "myStream", "scoped": false, "type": "STREAM", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_CEO-sGEhEeSIfKUUo5F2Xw" } ] scm set flowtarget my_compB_wksp myStream -r rtc_uat --flow-components compB The flow target was updated. scm list flowtargets -r rtc_uat my_compB_wksp -j [ { "current": true, "default": true, "name": "myStream", "scoped": false, "type": "STREAM", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_CEO-sGEhEeSIfKUUo5F2Xw" } ] scoped should be true here. The pending changes view still shows both components 
When I do the edit of the flow target in the GUI, only compB shows in the changes and the list flowtargets shows "scoped" : true. I have done this over and over. When I use streams created in RTC 3, I end up with a wonky flow target to the workspace itself. myStream was just created in RTC4 by copying one of the old RTC3 streams. I have two questions: 1. What is wrong with my commands - or is there a RTC bug? 2. Why is it doing the really wonly stuff when I operate on streams created in RTC3? well, now I have this one in the wonky state as well. I removed the flow target in the GUI and then added it again from scm. scm add flowtarget my_compB_wksp myStream -r rtc_uat The flow targets were added. scm list flowtargets -r rtc_uat my_compB_wksp -j [ { "current": false, "default": false, "name": "my_compB_wksp", "scoped": false, "type": "WORKSPACE", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_OldqoGEhEeSIfKUUo5F2Xw" }, { "current": true, "default": true, "name": "myStream", "scoped": false, "type": "STREAM", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_CEO-sGEhEeSIfKUUo5F2Xw" } ] scm set flowtarget my_compB_wksp myStream --flow-components compB -r rtc_uat The flow target was updated. scm list flowtargets -r rtc_uat my_compB_wksp -j [ { "current": false, "default": false, "name": "my_compB_wksp", "scoped": false, "type": "WORKSPACE", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_OldqoGEhEeSIfKUUo5F2Xw" }, { "current": true, "default": true, "name": "myStream", "scoped": false, "type": "STREAM", "url": "https:\/\/server:9443\/jazz\/", "uuid": "_CEO-sGEhEeSIfKUUo5F2Xw" } ] the flow target to itself cannot be deleted in the GUI, I have to remove the whole workspace. I think what it does is quite scary. |
Accepted answer
You are right that when you use --flow-components to the 'set flowtarget' command it should show scoped as true when you list the flow targets. By the way, did you try running 'scm list flowtargets -r rtc_uat my_compB_wksp -S'? I believe it will show all the components.
I believe the pending changes is showing both the components because the components did not get scoped. Please raise a defect.
By the way, does it work if you set the flow target to a stream created using RTC 4? Not sure if that should make any difference.
Martina Riedel selected this answer as the correct answer
Comments The -S only does something when the target is actually scoped.
I made myStream2 from scratch (using existing components) and it didn't change a thing.
I made a RFE. I believe it will create a RTC WI automatically.
That is not the right place to raise a defect. I have opened the following workitem to address this issue: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=336771 actually it is a good way to get the eyes on it that I want to notice it.
|
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.