Archiving and restoring configurations
You can archive streams and baselines that are no longer in use so that they are not
shown in the list of configurations. Archiving a configuration does not delete it; configurations
cannot be deleted. You can restore an archived configuration so that it is visible and available for
use by you or other team members.
Before you begin
- Ensure that you are familiar with project areas, baselines, streams, and change sets (if supported).
- Ensure that you are logged in to a project.
- Configuration management capabilities must be enabled for the project.
- You must have permission to archive configurations.
About this task
Archiving a configuration removes it from the list of active configurations. It is common to
archive a configuration when team members no longer work in it, or if the configuration is not a
flow target for other configurations. You might archive a baseline that was created for a review,
when the baseline is no longer required.
Note: You can archive all the configurations in a component
at the same time by archiving the component. See the related topic.
You cannot archive a baseline if another configuration has a dependency on it. You cannot archive a stream that is the flow target of another configuration.
Procedure
Jazz.net channel User Education channel |
Agile learning circle Learning circles |
developerWorks forums |
Deployment wiki Support blog |