Snapshot forcing baselines on components
Hello,
We have many components in our project. At each release we need to snapshot these components to mark a specific codebase. When we create a new snapshot on a Stream (for instance) RTC creates automatically baselines only for those components that have been modified since the last baseline. This causes lot of confusion because one release include different baseline names for different components. Is there any way to force all components in a workspace/stream to be marked with the same baseline name regardless if they have been modified or not when we create a snapshot in that workspace/stream? It would be very useful if we could extend the command create snapshot with an option "forcebaseline"... How about? Thanks in advance, Marco |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 26 '10, 8:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please identify the use cases where the baseline names matter ... there
might be a better way of handling those use cases than forcing the creation of redundant baselines. With continuous integration, builds are created very frequently, and generating new baselines for every component in every build could rapidly flood the repository with redundant baselines. This would be somewhat like creating a new version of every file whenever a baseline is created (so that all the versions can be given the same version id). Cheers, Geoff primeur.jazz.net wrote: Hello, |
|
Hi Geoff,
I agree with the problem of redundant baseline if you have a nightly build, but our context is quite different: Forcing baseline creation should be an option. BTW I try to describe better our need. The Context: We have to manage two (kinds of) Development Lines: - Library (LDL): which provides the basic components (each Library component is mapped on one RTC component). LDL has its own development stream. - Applications (ADLs) (one team for each application): which uses SOME library components, and assemble them to develop specific applications. Distinct ADLs work on distinct Development Stream (i.e. each ADL has its development stream). The Use Case: LDL releases a new version The steps we imagined are: - LDL create a snapshot on their Stream - Each ADL checks the differencies between the version of the component in their development stream and the new version of the component - Each ADL "replaces" (the ADL team leader decides when) the LDL components in their development stream - Each ADL needs to know exactly which LDL release is using for each component Any alternative way of handling our need? Cheers, Marco |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jan 28 '10, 4:08 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Marco,
In the scenario below, the the ADL integrator would invoke the "compare" operation with the desired snapshot (no need to specify any baseline names). Similarly, they would invoke the "replace with" operation on their integration workspace, and select the desired LDL release snapshot. This would then ask them whether they wanted to add/remove components (and they would respond "no", if they only use a selected subset of the LDL components). So I believe there is no need to ever look at the actual baseline names in the scenario you describe. Cheers, Geoff primeur.jazz.net wrote: Hi Geoff, |
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.