propagating changes between streams - revisited
I asked this question some time ago but never really got a clear understanding of how this works. Let me try to re-phrase the question...
I have several teams, each working on different parts of a project. Each team has it's own team area containing a team stream. I'd like to create a parent stream such that each team stream is a child to this parent stream. Furthermore I'd like the changes made in the child stream to be propagated to the parent stream. Since teach team works on differnt components, there should be no merge issues in the parent stream.
Simply setting the parent stream as the flow target of the individual team streams does not seem to flow the changes from child to parent. How is this accomplished?
As a side note: The parent stream happens to be a CC synchronized stream and also the basis for daily builds.
I have several teams, each working on different parts of a project. Each team has it's own team area containing a team stream. I'd like to create a parent stream such that each team stream is a child to this parent stream. Furthermore I'd like the changes made in the child stream to be propagated to the parent stream. Since teach team works on differnt components, there should be no merge issues in the parent stream.
Simply setting the parent stream as the flow target of the individual team streams does not seem to flow the changes from child to parent. How is this accomplished?
As a side note: The parent stream happens to be a CC synchronized stream and also the basis for daily builds.
5 answers
Changes never "automatically" flow. The user (or some script or
process) needs to explicitly "deliver" (to add changes from a workspace
to a stream or another workspace) or "accept" (to add changes from a
workspace or stream into a workspace).
Defining flow targets is just a way of specifying what the default
source should be for an accept and the default target should be for a
deliver.
You should be able to use the Jazz "build" machinery to schedule the
flow to occur automatically at the interval you specify (every hour, or
whatever).
Could someone from the Build or SCM team provide details on how to drive
those deliver/accept requests from the build?
Cheers,
Geoff
pravesh wrote:
process) needs to explicitly "deliver" (to add changes from a workspace
to a stream or another workspace) or "accept" (to add changes from a
workspace or stream into a workspace).
Defining flow targets is just a way of specifying what the default
source should be for an accept and the default target should be for a
deliver.
You should be able to use the Jazz "build" machinery to schedule the
flow to occur automatically at the interval you specify (every hour, or
whatever).
Could someone from the Build or SCM team provide details on how to drive
those deliver/accept requests from the build?
Cheers,
Geoff
pravesh wrote:
I asked this question some time ago but never really got a clear
understanding of how this works. Let me try to re-phrase the
question...
I have several teams, each working on different parts of a project.
Each team has it's own team area containing a team stream. I'd like
to create a parent stream such that each team stream is a child to
this parent stream. Furthermore I'd like the changes made in the
child stream to be propagated to the parent stream. Since teach team
works on differnt components, there should be no merge issues in the
parent stream.
Simply setting the parent stream as the flow target of the individual
team streams does not seem to flow the changes from child to parent.
How is this accomplished?
As a side note: The parent stream happens to be a CC synchronized
stream and also the basis for daily builds.
You can find a quick introduction to the SCM command line tool here:
https://jazz.net/wiki/bin/view/Main/SCMCommandLineTutorial
In addition I have two follow up questions:
1. Does anybody know where to find examples of this kind of multiple stream development? (ant build files,...)
2. Will RTC 1.0 include support to specify the stream(s) the build results need to flow to (e.g. integration streams)?
https://jazz.net/wiki/bin/view/Main/SCMCommandLineTutorial
In addition I have two follow up questions:
1. Does anybody know where to find examples of this kind of multiple stream development? (ant build files,...)
2. Will RTC 1.0 include support to specify the stream(s) the build results need to flow to (e.g. integration streams)?
> 1. Does anybody know where to find examples of this kind of > multiple stream development? (ant build files,...)
There are some example build scripts at:
$RTC_CLIENT_INSTALL\jazz\buildsystem\buildtoolkit\examples
> 2. Will RTC 1.0 include support to specify the stream(s) the > build results need to flow to (e.g. integration streams)?
Delivering to another stream after a successful build will be possible with 1.0. We don't have an example of doing this, but if you take one of the example build scripts, you could add a step at the end of the Ant script which would deliver using the command line client.
Jean-Michel Lemieux
Jazz Source Control Team
There are some example build scripts at:
$RTC_CLIENT_INSTALL\jazz\buildsystem\buildtoolkit\examples
> 2. Will RTC 1.0 include support to specify the stream(s) the > build results need to flow to (e.g. integration streams)?
Delivering to another stream after a successful build will be possible with 1.0. We don't have an example of doing this, but if you take one of the example build scripts, you could add a step at the end of the Ant script which would deliver using the command line client.
Jean-Michel Lemieux
Jazz Source Control Team