History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-78
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Robin Shen
Votes: 7
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Use wild chars to specify permission for multiple configurations

Created: 10/May/06 06:03 AM   Updated: 24/Sep/09 08:03 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
From Mike,

I need to limit the permissions on more than a dozen configurations, each with mutliple release scenarios and I was wondering if I can create an OGNL expression that will map to many configurations. For example, we have the following structure:

root.Service-tier.common.Continuous_build
root.Service-tier.common.Nightly_build
root.Service-tier.common.Release_major
root.Service-tier.common.Release_minor
root.Service-tier.common.Release_bug

root.Service-tier.tax.Continuous_build
root.Service-tier.tax.Nightly_build
root.Service-tier.tax.Release_major
root.Service-tier.tax.Release_minor
root.Service-tier.tax.Release_bug

root.Service-tier.activity.Continuous_build
root.Service-tier.activity.Nightly_build
root.Service-tier.activity.Release_major
root.Service-tier.activity.Release_minor
root.Service-tier.activity.Release_bug

and many more.

In the Groups section, I would like to create a new Configuration subtree that will allow the following "build" only priveledges:

root.Service-tier.*.Release*

This way, developers can make changes and updates to the Continuous and Nightly builds, but only have "build" Permission to the Release builds. Is this possible?

Thanks,

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.