A single build engine shared between multiple project areas
Hi,
Is it possible to share a build engine between 2 project areas? I have Project Area A with Build Engine 1. I then defined Project Area B. I have builds jobs on B I would like run. However, they stay pending.
I have tried running 2 build engines on the same server with different IDs and userids, but they both end up having errors fetching the files.
Does anyone have any ideas on how to work around this?
Cheers,
Michael
Is it possible to share a build engine between 2 project areas? I have Project Area A with Build Engine 1. I then defined Project Area B. I have builds jobs on B I would like run. However, they stay pending.
I have tried running 2 build engines on the same server with different IDs and userids, but they both end up having errors fetching the files.
Does anyone have any ideas on how to work around this?
Cheers,
Michael
2 answers
It is possible to use a single engine for multiple definitions that live in
different project areas. In the definition editor, you should be able to see
your shared engine in the Supporting Build Engines section and select it.
Note however that the engine does have a single team area association which
will control permissions. Also, the engine will only be visible in the Team
Artifacts view under the associated team's project area. These issues should
not cause a problem or prevent you from sharing the engine.
---
Ryan Manwiller
Jazz Team Build
different project areas. In the definition editor, you should be able to see
your shared engine in the Supporting Build Engines section and select it.
Note however that the engine does have a single team area association which
will control permissions. Also, the engine will only be visible in the Team
Artifacts view under the associated team's project area. These issues should
not cause a problem or prevent you from sharing the engine.
---
Ryan Manwiller
Jazz Team Build