Supported Build definitions selection in build engine

On 2010/10/28 7:38, vrcampbell wrote:

We are using RTC 2.0.0.2 iFix2. We have 2 build servers, one for
development and one for production. The admin staff maintains the
Build Engines for both servers, but the developers maintain the build
definition for their development builds. We want to prevent the
developers from selecting a production build server in the
"Supporting Build Engines" section of the Build Definition.
It would appear that this can be determined by the "Build
Definitions" section of the Build Engines, by selecting which
build definitions are supported by the build engines. However, it
doesn't seem like this works. We have no build definitions selected
in any of our build engines, but all our build definitions can select
and use any build engine. How can I prevent a development build
definition from selecting a production build engine?

You need to set the permissions of the build engines so that only the
admin staff can modify them. If the developers don't have permission to
modify the build engines, they can't establish the link between the
build definition and the build engine.

Never having had to do this personally myself, I unfortunately can't
tell you exactly how to do it. But I'm pretty sure it involves tweaking
the process of the team area that owns the build engines.

The "Supporting Build Engines" section of a build definition and the
"Build Definitions" section of a build engine are just two different
views of the same thing. To create a link between a build engine and a
build definition, you can check the box in either place. The behavior
is the same whether you check the box in the build engine or the build
definition.

--
David Olsen
IBM Rational

Thanks, David. I've altered my access, removing "Save Build Engine", and it does not allow me to save my build definition if I select a different build engine. The only downfall that I see is that this is an all or nothing solution, that developers cannot choose which development build engine(s) to use because we do not want them to use a production build engine.

On 2010/10/29 6:38, vrcampbell wrote:

The only downfall that I see is
that this is an all or nothing solution, that developers cannot
choose which development build engine(s) to use because we do not
want them to use a production build engine.

This may or may not be worth the effort, but I think you can do what you
want by having the build engines owned by two different team areas. The
development build engine would be owned by the development team area,
and all the developers would have permission to change it. The
production build engine would be owned by a different team area
(possibly a team area that exists only for the purpose of owning that
build engine), where only the admin folks would have permission to save
build engines.

That's correct. The engine/definition mapping is maintained on the engine, so the Save Build Engine operation's permissions in the engine's process area determine who can or cannot add a definition to an engine, whether it's done via the engine editor or the definition editor.