Delivering to alternate flow target
![]()
I changed the flow target of my repository workspace from team's stream to another developer's repository workspace and tried to deliver change sets to it. I get an error as: "Permission denied. only the owner of the repository ws can modify it".
How do I overcome this? Thanks! |
4 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 12 '09, 6:37 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You share work with other developers by delivering to a shared stream,
not by delivering directly into their workspaces (a developer needs to be able to decide when they want to "accept" changes into their workspace ... they shouldn't have their workspace configuration disrupted at arbitrary times by another developer delivering into their workspace). So you are allowed to deliver to a workspace only if you own that target workspace. To avoid this kind of confusion, I've submitted work item 87494, suggesting we never allow delivering to a workspace (since you can always achieve the same effect by "accepting" into that workspace). Cheers, Geoff theju wrote: I changed the flow target of my repository workspace from team's |
![]()
Hi
As far as i know, RTC is able to set flow target from repository workspace to another repository workspace which belong to another user. I knew that repository workspace has an owner, so if another user would like to deliver his change to repository workspace, he won't be allow. Have everyone had any solution. Chatchawun J. |
![]() Hi I think you should follow the best practice suggested by Geoff, avoid delivering from workspace to workspace. Obviously next release may block this type of operations. Jirong |
![]()
If it's something that isn't ready to release to stream but another developer wants to use the code, the other developer can accept your changes. He would change the flow target of his workspace to your workspace and accept changes. He can modify his own workspace so he should be accepting instead of you delivering.
|