Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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!

0 votes



4 answers

Permanent link
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
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!

0 votes


Permanent link
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.

0 votes


Permanent link
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.


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

0 votes


Permanent link
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.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jul 12 '09, 8:03 a.m.

Question was seen: 5,072 times

Last updated: Jul 12 '09, 8:03 a.m.

Confirmation Cancel Confirm