How to create a stream with cli specifying both the project and owning team?
![]() A customer wants to create streams via a script and would like to specify the specific project (he works with several) and the owning team. He has run into several problems. First of all, you can't seem to specify both --projectarea and --teamarea in the same command. This seems to be a deficiency / limitation of the create stream syntax. Secondly, and maybe more importantly, is that the customer wants to use the text/label method to specify the project and/or team area. The reason this is a problem is that multiple projects have a team with the same label. So if he specifies the project/teamarea with a label RTC may pick the wrong project / owning team. I have suggested he has two options then, first to create the stream by specifying the owning team by a relative ID or UUID (which you will have to predetermine via a list command). The second method would be by using two commands, first to create the stream in the correct project and then secondly using the lscm set attributes command with the --ownedby option. It turns out that even when the owning project is known after the first command (create stream --projectarea) he still had failures when executing the second command if he uses the label. It appears that even though the team is unique in the project it was created in, RTC still looks over teams in other projects when searching via label so he had to use a relative or UUID for the owning team anyway.
|
2 answers
![]() The 'lscm set attributes' command also works in the same way as other commands which looks for team area in the repo and will fail if the name matches multiple team areas.
I don't think there is any other way to do this as of today. Please go ahead and raise a support request.
|
![]() There is no need to specify the project area and the team area at the same time. If the stream will be owned by a team area, it is sufficient enough to just specify the team area. Your challenge is that you want to use the name as the identifier of a team area, which will not work as Shashikant pointed out.
|
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.