RTC 3.0 Streams - many versus few
I have a situation where I have 180+ components and most of the components are autonomous (without inter-dependencies). This is for a zOS environment where we intend to use dependency builds and promotes. The stream setup will be a fairly typical DEV, TEST, PROD. I could put all the components under a single DEV, TEST, PROD stream or I could create a number of DEV, TEST, PROD streams with a few components under each. Either way I will probably need component level builds to support promotes and personal dependency builds where only one component gets loaded into a workspace.
I would love to hear the pros/cons of many streams versus single or few streams. |
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 21 '10, 2:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The main comment I'd make is that I'd avoid having 180+ components in a
single stream. It slows down the GUI significantly, and I believe it slows down the build as well (folks from the build team should confirm/deny that observation). So I'd look for some logical grouping which results in 10-20 components per stream. Cheers, Geoff On 12/21/2010 6:23 AM, dpoulin wrote: I have a situation where I have 180+ components and most of the |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.