Group DevOps applications into a product
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- DevOps
Products that use an application model in the CSDM support hierarchies of applications. You can customize hierarchies to simplify tracking of "rolled-up" data on DevOps Insights reports. This is used for the Product filter in insights.
Before you begin
Role required: application owner, sn_devops.admin
About this task
For example, you can include multiple DevOps microservice applications into a product, include multiple such products into a portfolio, and then include ("roll up") the portfolio in an organization. Another example structure might be application > team > product > portfolio or business unit.
- A DevOps application can belong to one or multiple products.
- A product or multiple products can belong to one or multiple other products.
- Multiple applications and products can belong to a product.
For every product, the system creates a corresponding entry in the application model and SDL component tables.
Procedure
Result
The DevOps Insights tabs provides filters for the reports.
- The scheduled "Data collection" job processes your changes. When the job finishes, you can view reports for the added products. If you are running the job manually, execute the "Update Repo Details and Work Item State Detail" job before executing the Data collection job.
- The Application filter lists all applications.
- The Product filter lists all applications plus all products.
- To view the members of a product, view the list in the Model category of
component table
(
<instanceName>/cmdb_m2m_model_component_list.do
). Applications are listed in the Component column and products are listed in the Bundle column.