It's all about the answers!

Ask a question

How can I enable source code checkin approval? (solved)


Harald Lahner (28810) | asked Oct 21 '11, 12:39 p.m.
Hi all,

we want to enable source code check-in or deliver approval for a specific SCM stream but leaving the other streams without approval.

When checking from "Team Configuration --> Operational Behavior" the operation "Deliver (server)" there are some preconditions, but none of them seems to meet our needs.

The precondition "Require Work Item Approval" works on the whole project area, not just single streams.

The precondition "Restrict Change set delivery to components in a stream" can be configured to work on single streams, but does not offer an approval feature.

Is there another way to enable a checkin or delivery approval or have you written your own precondition that can perform this tasks?

We are running RTC v2.0.0.2 iFix 6.

Thanks!

2 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 21 '11, 5:59 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The process preconditions that apply to a stream are determined by the
process area (project or team area) that owns that stream (you can
change the owner of an existing stream, in the stream editor).

So if you want different preconditions for different streams, make
different process areas the owner of those streams.

On a terminology note, you "checkin" to a change-set, and "deliver" to a
stream. There are process checks on deliver, but not on check-in (you
need to always be able to checkin your work, in order to ensure you can
always save its contents into the repository).

Cheers,
Geoff

On 10/21/2011 12:53 PM, hal wrote:
Hi all,

we want to enable source code check-in or deliver approval for a
specific SCM stream but leaving the other streams without approval.

When checking from "Team Configuration --> Operational
Behavior" the operation "Deliver (server)" there are
some preconditions, but none of them seems to meet our needs.

The precondition "Require Work Item Approval" works on the
whole project area, not just single streams.

The precondition "Restrict Change set delivery to components in a
stream" can be configured to work on single streams, but does not
offer an approval feature.

Is there another way to enable a checkin or delivery approval or have
you written your own precondition that can perform this tasks?

We are running RTC v2.0.0.2 iFix 6.

Thanks!

permanent link
Harald Lahner (28810) | answered Dec 01 '11, 8:56 a.m.
Hi all,

I have created the following solution which works very well for our teams:

1. Create a new role "SCM Approvers" and add it to all persons that should be approvers.

2. Create a new timeline beneath Main Development named "SCM stabilizing work".

3. Create a new team area "SCM stabilizing team" which holds all people that are working on stabilizing the code (usually the development team)
3a. Make the "SCM Stabilizing work" timeline the default for the newly created team.

4. Modify the process configuration for the new timeline
Team Configuration --> Timelines --> "SCM stabilizing work" --> Operation behavior
4a. Select the operation "Deliver (client) and enable "Preconditions ..."
4b. Add "Require work item approval"
4c. Add under "Required approvals" a new condition of type "Approval" and with 1 "SCM approvers"
(Note: Adding a larger number of approvers, at least this number of approvers must approve)

5. Select the SCM stream for which you want to enable the approval
and set the new owner of the stream to the "SCM stabilizing team"

Now the stream needs an approval of the work item, every time a developer wants to deliver a change.

When done with the approval time frame (e.g. The project is shipped and development returns to normal) you simply change back the owner of the stream to "Main Development" and the approval is not needed any more.
To re-enable the approval simply change the owner of the stream to "SCM stabilizing team".

I hope this helps all who have the same problem like me.

Cheers,
Harold.

Your answer


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