Managing Build engine permissions in an enterprise environment, help!
we have a centrally administered build farm. we created a special public project to hold the build engines, and the prototype build definitions for the different services the builders provide (static analysis, personal build, ...)
but we have run into a problem with only two apparent ways out (neither of which we want to use)..
when a user creates a build definition, they select a build engine (or engines) to run it on.
then press Save.. they get a permission denied, cause they are not allowed to modify the build engine.
this is because the build defs and build engines point to each other...
the ways out
1. enable modify build engine for everyone
2. add everyone (one by one or in groups) as users of the special project, with a 'Config mgr' role that enables this
(just as bad functionally as 1, but controlled funnel.
we do not want ANYONE other than central staff to be able to modify a build engine. but we don't have the staff or turnaround time to support creating build defs for each developer.
is there another way to solve this problem?
thanks