Moving components between servers (repositories)
Now my question: Is this the right behavior or is this a bug?
One more question: Is there a specific permission to allow/prevent this operation. The replicate permission doesn't work.
And what about change sets? Is a user allowed to flow change set to a destination where he is not allowed to deliver an entire component?
Many thanks for clarification in advance.
Cheers, Christine
Accepted answer
What some of the reference material above fails to mention is that a delivered component exists only one time in the remote repository which leads to the permission concerns and no small amount of user confusion.
One other answer
Please see
for considerations around permissions.
Comments
In our Project Setup the mentioned permissions for Source Control are included in used role itsself. But nevertheless I got the mentioned error + details: The operation is not governed by process. (distributed SCM is enabled)
Do you have one more idea?
Many Thanks, Christine
What puzzles me is that the error says "User 'x' does not have permission to read component 'y'. (Deliver operation). So somehow the user is not able or does not have the permission/access to the owning project area of the component.
I'd try to have the user create a repository workspace on that machine first and try to load all components. If that works have a new stream/repository workspace created on the other side. And try if the user can load the distributed workspace. Then try to deliver on this server.
Please also note, that the component does not move. A new component is created and then the change sets are replicated into the other server. The change sets will be on both servers and you will have two components that are associated, but live on different servers..
Many thanks, the reaseon for this misbehavior was the ownership of the component.