Sharing components in several streams
Is there a way to share a component in several streams without making a "copy" of it when adding the component from the stream editor.
The underlying use case is:
I have 2 streams X & Y that share the same component.
I would like to deliver changes in the the stream X and these changes becomes available in the stream Y.
I tried to add flow targets, thinking my changes will be "cascading" delivered through the flow graph. But it does not work.
However, in the last paragraph of the help topic "Adding and removing stream flow targets", we can read :
<< By default, all components in the stream flow to and from all of the stream's flow targets ... >>
What is wrong ?
Maybe the help is obsolete.
What is the real goal of stream flow concept ? (except having a visual representation of the stream interactions)
The underlying use case is:
I have 2 streams X & Y that share the same component.
I would like to deliver changes in the the stream X and these changes becomes available in the stream Y.
I tried to add flow targets, thinking my changes will be "cascading" delivered through the flow graph. But it does not work.
However, in the last paragraph of the help topic "Adding and removing stream flow targets", we can read :
<< By default, all components in the stream flow to and from all of the stream's flow targets ... >>
What is wrong ?
Maybe the help is obsolete.
What is the real goal of stream flow concept ? (except having a visual representation of the stream interactions)
4 answers
Is there a way to share a component in several streams without making a "copy" of it when adding the component from the stream editor.
Technically when you add a component to several streams we don't copy either the change-sets or the configuration. The underlying implementation shares as much as possible.
The underlying use case is:
I have 2 streams X & Y that share the same component.
I would like to deliver changes in the the stream X and these changes becomes available in the stream Y.
The tool doesn't automatically cascade deliveries. And the flow targets between streams are currently just used to initialize the flow targets of any repository workspace created from the stream. There is however nothing technically difficult to support cascading deliveries and we have an enhancement request somewhere to allow this.
For now, you'll have to deliver to both stream X and Y via the Pending Changes view.
Jean-Michel
Jazz Source Control Team
You might wish to see how we demonstrate this in the Jazz User Workshop
material on Jazz.net. In particular, the topic: Project Growth and
Multi-stream Development. Here we show how changes in a common component
shared between multiple teams are managed. There is an animated slide
for that topic that shows this visually and the exercise walks you
through the UI gestures. I am sure there are a variety of use cases here
but this will show you one common on.
The workshop material is available here:
https://jazz.net/learn/LearnItem.jsp?href=content/docs/workshop/index.html
ist-support wrote:
material on Jazz.net. In particular, the topic: Project Growth and
Multi-stream Development. Here we show how changes in a common component
shared between multiple teams are managed. There is an animated slide
for that topic that shows this visually and the exercise walks you
through the UI gestures. I am sure there are a variety of use cases here
but this will show you one common on.
The workshop material is available here:
https://jazz.net/learn/LearnItem.jsp?href=content/docs/workshop/index.html
ist-support wrote:
Is there a way to share a component in several streams without making
a "copy" of it when adding the component from the stream
editor.
The underlying use case is:
I have 2 streams X & Y that share the same component.
I would like to deliver changes in the the stream X and these changes
becomes available in the stream Y.
I tried to add flow targets, thinking my changes will be
"cascading" delivered through the flow graph. But it does
not work.
However, in the last paragraph of the help topic "Adding and
removing stream flow targets", we can read :
By default, all components in the stream flow to and from all
of the stream's flow targets ...
What is wrong ?
Maybe the help is obsolete.
What is the real goal of stream flow concept ? (except having a visual
representation of the stream interactions)
Also note that there is an Eclipse preference:
Team -> Jazz Source Control -> Changes :
Filtering in Pending Changes view : Flow targets : Show all (advanced)
If you select that preference, you can see your outgoing changes to
multiple targets, which makes it easier to deliver to multiple targets.
Cheers,
Geoff
jlemieux wrote:
Team -> Jazz Source Control -> Changes :
Filtering in Pending Changes view : Flow targets : Show all (advanced)
If you select that preference, you can see your outgoing changes to
multiple targets, which makes it easier to deliver to multiple targets.
Cheers,
Geoff
jlemieux wrote:
ist-supportwrote:
Is there a way to share a component in several streams without making
a "copy" of it when adding the component from the stream
editor.
Technically when you add a component to several streams we don't copy
either the change-sets or the configuration. The underlying
implementation shares as much as possible.
ist-supportwrote:
The underlying use case is:
I have 2 streams X & Y that share the same component.
I would like to deliver changes in the the stream X and these
changes becomes available in the stream Y.
The tool doesn't automatically cascade deliveries. And the flow
targets between streams are currently just used to initialize the
flow targets of any repository workspace created from the stream.
There is however nothing technically difficult to support cascading
deliveries and we have an enhancement request somewhere to allow
this.
For now, you'll have to deliver to both stream X and Y via the Pending
Changes view.
Jean-Michel
Jazz Source Control Team