Problems delivering change set to multiple streams
In my RTC server we have it configured to ensure a review approval has been done prior to code delivery. This works very well, but when I redirect my workspace to deliver into another stream it says I do not have a review approval. We are doing this to merge two streams together and it means we need to go to a whole load of work items and rereview them. Is there some other way?
Thanks Alasdair |
5 answers
|
Having done further investigation even getting a second review doesn't allow it to be delivered. I have to disable the prereq check for an approved review.
Has anyone else seen this or know how to get around it? Alasdair |
Jared Burns (4.5k●2●9)
| answered Apr 08 '09, 1:02 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On Wed, 08 Apr 2009 16:57:39 +0000, alasdair wrote:
Having done further investigation even getting a second review doesn't It sounds like your setup is something like this: ProjectAreaX defines: RoleX precondition: require delivered change set reviewed by RoleX contains: TeamA assigns RoleX to UserX owns StreamA TeamB owns StreamB When you deliver a change set reviewed by UserX to StreamA, the precondition passes because UserX is assigned RoleX in TeamA. But when you deliver the same change set to TeamB, it fails because UserX is not assigned RoleX in this team. Does this sound like what's happening? If so, here are a few possible solutions: 1. Assign RoleX to UserX in TeamB 2. Assign RoleX to UserX in ProjectAreaX 3. Remove the precondition from ProjectAreaX and add this precondition to TeamA only 3. Leave the precondition on ProjectAreaX, but make it overrulable. Optionally, you can also add the precondition to TeamA and make it not overrulable there. 4. Do not deliver individual change sets to TeamB, but deliver baselines instead. (This is how the RTC team usually works) -- Jared Burns Jazz Process Team |
|
There appear to be two controls. In Operation Behavior I can configure:
Source Control > Deliver (client) Source Control > Deliver (server) On the client side we have set "Require Work Item Approval" to be team-member. Everyone has team-member authority to the project area. On the server side we have set "Ensure Delivered Change sets Reviewed". If we disable the server side behavior we can deliver the changes, which makes me think it is this check that is causing the problem. The description says: Ensures that change sets being delivered have an approved review task. It allows specifying the reviewers by name or by role. I can find no way to specify any roles, or configure the behavior in any way. I am concerned that disabling the server side check could allow un-reviewed code to be delivered, even though the client side check is enabled. Can you tell what I am missing here? I am using 1.0.1. Thanks Alasdair |
does the person granting the review approval have the same role/permissions on the teams that own the streams? it was a minor oversight we had before in our process.
ciao! |
does the person granting the review approval have the same role/permissions on the teams that own the streams? it was a minor oversight we had before in our process. I didn't initially, but I have given myself authority to all the teams and it still didn't work. Alasdair |
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.