Delete a Stream - any side-effects?
Hi
We created, based on our "main development line" - Stream, another one.
There we tried some things, which finally worked. These changes were
then delivered back to our "main development line" - Stream (via a
repositpory workspace of course). So, our experimental stuff stream does
not contain any change sets, which the main development line stream
doesn't have, too. Means, the former experimental stuff is now part of
the product and the experimental streams content is outdated.
Can we delete the experimental stream without risk or will this
interrupt/corrupt the "change flow"/"change set series" on our main
stream, as the changes were intially delivered to the experimental
stream? Or can we corrupt the repository workspaces, which still have
the experimental stream as optional or active flow target?
Thanks and kind regards,
Stefan
We created, based on our "main development line" - Stream, another one.
There we tried some things, which finally worked. These changes were
then delivered back to our "main development line" - Stream (via a
repositpory workspace of course). So, our experimental stuff stream does
not contain any change sets, which the main development line stream
doesn't have, too. Means, the former experimental stuff is now part of
the product and the experimental streams content is outdated.
Can we delete the experimental stream without risk or will this
interrupt/corrupt the "change flow"/"change set series" on our main
stream, as the changes were intially delivered to the experimental
stream? Or can we corrupt the repository workspaces, which still have
the experimental stream as optional or active flow target?
Thanks and kind regards,
Stefan
One answer
You can safely delete the experimental stream.
In general, you can always delete any stream, without disrupting the
configuration of a workspace or any other stream.
Note: You will probably want to delete references to that stream from
any workspace that has that stream as a flow target ... but you can do
that cleanup after you have deleted the stream.
Note: Change-sets exist independently of any stream, so deleting a
stream does not delete any change-sets.
Cheers,
Geoff
Stefan Stern wrote:
In general, you can always delete any stream, without disrupting the
configuration of a workspace or any other stream.
Note: You will probably want to delete references to that stream from
any workspace that has that stream as a flow target ... but you can do
that cleanup after you have deleted the stream.
Note: Change-sets exist independently of any stream, so deleting a
stream does not delete any change-sets.
Cheers,
Geoff
Stefan Stern wrote:
Hi
We created, based on our "main development line" - Stream, another one.
There we tried some things, which finally worked. These changes were
then delivered back to our "main development line" - Stream (via a
repositpory workspace of course). So, our experimental stuff stream does
not contain any change sets, which the main development line stream
doesn't have, too. Means, the former experimental stuff is now part of
the product and the experimental streams content is outdated.
Can we delete the experimental stream without risk or will this
interrupt/corrupt the "change flow"/"change set series" on our main
stream, as the changes were intially delivered to the experimental
stream? Or can we corrupt the repository workspaces, which still have
the experimental stream as optional or active flow target?
Thanks and kind regards,
Stefan
Comments
Hi Geoff,
We have several streams that are no more required,
Will a delete stream help in recovering space in the DB ? Is it recommended to delete streams to reclaim the space occupied by unwanted files?
Do we have any impact on the history of the stream/component/files.
In short, Im looking at ways to control the growth of the DB from unwanted streams.
One other thing to note is that if you have created snapshots of that stream you want to delete, you will be prompted to select new owners of those snapshots.