How to give persmission to request only specific build
Hello.
Our team use RTC and Jazz Build Engine. We have more test environmenst and more builds. Each of build can deploy new code to one environement. But only some developers can deploy to every enironments (reqeust all builds), another developer have permission only for some environemnts.
On example. Environment Alpha and Beta. Alpha is used by developer for developing and time to time, is code promoted to Beta environment. This promote execute only Project Manager (Architect, Leader). Build_ALPHA deploy data to alpha, and Build_BETA deploy data to beta environment.
How to give permission for request Build_BETA only to Project Manager?
Our team use RTC and Jazz Build Engine. We have more test environmenst and more builds. Each of build can deploy new code to one environement. But only some developers can deploy to every enironments (reqeust all builds), another developer have permission only for some environemnts.
On example. Environment Alpha and Beta. Alpha is used by developer for developing and time to time, is code promoted to Beta environment. This promote execute only Project Manager (Architect, Leader). Build_ALPHA deploy data to alpha, and Build_BETA deploy data to beta environment.
How to give permission for request Build_BETA only to Project Manager?
One answer
Hi Lukas,
In general, process permissions for builds are controlled by the user's supported role(s) in the project or team area associated with the build definition (or build engine for some operations, like changing the definitions supported by the engine). So for a given area, you can say 'only users with the ProjectManager role can Request a Build' or 'Everyone can Request a Build' but you can't have different permissions for different build definitions in the same team area.
So you could create separate child team areas; Team M for managers and Team D for developers, and change the build definitions' team areas accordingly.
Note that permissions are generally looked up from the child team area, to the project area, including any intermediate parent team areas. So you could associate the restricted builds with the project area instead of the team area, and give only managers permission to request builds there. This would avoid having to create separate team areas.
You can also use the 'Restrict the Users Requesting a Build' precondition, which basically lets you override the parent process area lookup: it restricts the operation to only direct members of the project or team area associated with the build definition.
In general, process permissions for builds are controlled by the user's supported role(s) in the project or team area associated with the build definition (or build engine for some operations, like changing the definitions supported by the engine). So for a given area, you can say 'only users with the ProjectManager role can Request a Build' or 'Everyone can Request a Build' but you can't have different permissions for different build definitions in the same team area.
So you could create separate child team areas; Team M for managers and Team D for developers, and change the build definitions' team areas accordingly.
Note that permissions are generally looked up from the child team area, to the project area, including any intermediate parent team areas. So you could associate the restricted builds with the project area instead of the team area, and give only managers permission to request builds there. This would avoid having to create separate team areas.
You can also use the 'Restrict the Users Requesting a Build' precondition, which basically lets you override the parent process area lookup: it restricts the operation to only direct members of the project or team area associated with the build definition.