Content Lifecycle Management
Content lifecycle management allows you to customize repositories and test packages before updating production clients. This is especially useful if you need to apply updates during a limited maintenance window.
This is achieved through a series of environments that your software channels can move through on their lifecycle. Most environment lifecycles include at least test and production environments, but you can have as many environments as you require.
When you have created your project, defined environments, and attached sources and filters, you can build the project for the first time. For more information about content lifecycle management, see administration:content-lifecycle.adoc.
When your project is built successfully, you need to add the new channel to an activation key. For more information about custom channels, see administration:custom-channels.adoc.
Go to, create a project and assign it a label and a name. Then use Attach/Detach Sources to attach a base channel and child channels, and finally save.
You can use Attach/Detach Filters to fine tune what packages to include in the resulting channel. A number of filters are available: name, date, synopsis, reboot required or not, etc.
At this point you can define your environments by clicking Add Environment in the
Environment Lifecycle dialog.
Test and Production are usually the bare minimum most customers have but you may need more.
Continue creating environments until you have all the environments for your lifecycle completed.
The final step is building the project, which can take a little while.
For more information about content lifecycle management, including worked examples , see administration:content-lifecycle.adoc.