Multiple Stream Targets for single change set
Hi,
I want to know whether setting multiple stream targets for a single change set is possible ? Actually we are maintaining two streams and I want ensure that what ever code delivered into one stream should be automatically delivered to the second stream as well. Is this can be achieved from setting flow targets ?
I want to know whether setting multiple stream targets for a single change set is possible ? Actually we are maintaining two streams and I want ensure that what ever code delivered into one stream should be automatically delivered to the second stream as well. Is this can be achieved from setting flow targets ?
4 answers
You can deliver your changes from one stream to another.
You can do so by enabling the post build activities in your build definition. You can further specify when to deliver the changes to the target stream - when build succeeds or always. You can also select which components to deliver.
You can do so by enabling the post build activities in your build definition. You can further specify when to deliver the changes to the target stream - when build succeeds or always. You can also select which components to deliver.
I do not know of a way to automatically flow to multiple targets.
There are lots of do multi-stream maintenance. Assuming you have a service & a "trunk" stream, here's what I would do:
There are lots of do multi-stream maintenance. Assuming you have a service & a "trunk" stream, here's what I would do:
- Create a maintenance workspace; primary flow target is the maintenance stream.
- Make fix(es)
- Deliver fix(es) to maintenance stream
- Change flow target to trunk stream
- Accept all
- Merge as necessary to resolve conflicts; rework fix(es) as needed
- Deliver fix(es) to trunk stream
- Change flow target back to maintenance stream
-
Discard outgoing changesets
Hello Maruthi,
You are able to deliver change sets automatically between steams using the provided build functionality. Please see delivering change sets automatically between steams from the article cool hidden features in RTC.
You may also manually submit changes between steams by adding both steams in the flow target. Right click the steam and select Show>>Pending Changes.
You are able to deliver change sets automatically between steams using the provided build functionality. Please see delivering change sets automatically between steams from the article cool hidden features in RTC.
You may also manually submit changes between steams by adding both steams in the flow target. Right click the steam and select Show>>Pending Changes.
You can set one stream as a flow target of another to keep then in sync. For stream to stream flow targets, they are not by-directional, so each stream will need to set the other as a flow target.
For example, if there are two streams A and B, where B is configured to be a flow target of a. When a change set is delivered to stream A, the change set will then appear in the pending change view of stream B. this change set wil then need to be accepted by stream b.
However if a change set is delivered to stream B, it will not appear in the pending view of stream A.
For example, if there are two streams A and B, where B is configured to be a flow target of a. When a change set is delivered to stream A, the change set will then appear in the pending change view of stream B. this change set wil then need to be accepted by stream b.
However if a change set is delivered to stream B, it will not appear in the pending view of stream A.