TTE/Server move to Cartwright
- Had AD groups created in one day!
- Supported the server move to Cartwright. The move invalidated all Clearcase/Multisite licenses! Got emergency licenses
" />
« June 2004 | Main | August 2004 »
Implemented Permissions trigger.
I've given the "permissions trigger" some thought and would like to formalize the requirements a bit. The new trigger will have the following characteristics:
Let's see an example of how this will work and how the trigger will respond. Let's assume the following directory structure:
Core_automationEmpower CC-EAG-AS, CC-EAG-ESBFunctions CC-EAG-VIP
Results CC-EAG-VMS
Common
Further let's assume that the permissions element is at the Empower level and contains the groups CC-EAG-AS and CC-EAG-ESB. This says that those two groups (as well as CC-TTE as primary group owners of the vob) have write permission (the ability to checkout) elements from Core_automation/Empower downward. Additionally let's say that we have a permissions element at Empower/Functions that lists CC-EAG-VIP and Empower/Results has a permissions element that lists CC-EAG-VMS. The following can be said:
The pseudo code for the trigger is roughly as follows. Note that the trigger gets fired during checkout of an element only (it is assumed if the user successfully checked out the element then, at the time, he had write permissions and should be allowed to check in the element):
$vob_group_owner = GetGroupOwner (vob)
$current_group = GetCurrentGroup (CLEARCASE_PRIMARY_GROUP as per "creds")
if (permissions element exists in the current folder) {
if (IsAMember (Parse ($permissions_element), $current_group) {
<allow checkout>
} else {
<recurse to check parent folder stopping at vob root>
<disallow checkout>
}
}
Created various views to perform performance testing of PowerBuilder builds.