Home
Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
Solution versions

Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
- Creating value streams
  Create a value stream and then customize it by defining phases and stages that reflect your typical workflow.
- Viewing value streams
  Viewing value streams using list and card view layouts.
- Value stream metrics
  Assess project quality, progress, and performance with the HCL DevOps Velocity (Velocity) metric data tools.
- Navigating value streams
  Manage a value stream's displayed data by applying filters and queries.
- DevOps query language
  Use the DevOps query language to filter the information displayed in your value stream.
- External YAML configuration
  You can create a minimal value realization of different DevOps tools into HCL DevOps Velocity (Velocity) quickly using external YAML configuration file.
- Pipelines
  Pipelines provide a streamlined method to manage the applications in your development lifecycle. With pipelines, you can auto-generate deployment plans and deploy applications versions to all environments.
- Solution versions
  - Enabling the solution version feature on DevOps Velocity
    When you want to use the solution version on HCL DevOps Velocity (Velocity), you must enable it.
  - Adding an application to the pipeline
    You can add an application to the pipeline in HCL DevOps Velocity (Velocity).
  - Creating the solution version
    You can create a solution version in the pipeline stage with combination of application versions.
  - Editing the draft solution version
    You can edit the draft solution version to update name, description, and application version combinations.
  - Publishing the draft solution version
    You can publish the draft solution version in the pipeline stage to lock the application versions.
  - Deploying the solution version
    You can deploy the solution versions in the environments.
  - Unlinking the solution version
    You can unlink the solution version from the pipeline stage.
  - Deleting the solution version
    You can delete the solution version permanently from the pipeline stage when it is not required.

Solution versions

Solution version is a combination of different versions of one or more applications in a pipeline.

You can use a solution version to combine the required application versions from the pipeline and deploy them to different stages. A solution version includes the application versions that are tested and working in a stage and can be deployed into any stage in the pipeline. You can roll back or upgrade the version of applications in the solution version. You can add only the compatible combinations of application versions to the solution version.

The solution version is built incrementally to ensure that the tested combinations are included. You can create only one solution versions with a combination of deployed applications versions in a stage. You can deploy the solution version created in a stage into other stages in the pipeline.

During the build phase, a solution version is called a solution draft version. Any changes to the deployed application versions of a draft solution version in a stage are updated automatically in the solution version inventory. You can edit the combination of applications by editing the draft solution version. After the solution version is published, the version of the solution version is locked and its inventory cannot be updated.

When a new solution version is deployed in the stage where there is already a solution version is deployed, then the published solution version is either reverted to draft status or removed completely.