Organize flow outputs
This page shows you how to organize the outputs of different variations of flows by configuring the
flavor attribute. Once configured, flow outputs are meaningfully grouped in the WVS Web Client.
Why organize flow outputs
For large projects, you might want to create variations of the same flows. For example, your team creates two variations of the build flow that each create outputs targeting different stakeholders. One variation,
myBuild1, creates builds for the QA team and has debug information on the screen. Another variation,
myBuild2, creates builds for executive review and does not include debug information on the screen.
To help the team keep track of which outputs are intended for which stakeholder, you can configure the
flavors attribute of
execReview, respectively. Once configured, the output of these two flows are grouped under
execReview when you view them in the Build Browser of the WVS Web Client.
To configure the
flavor attribute of a flow, run the following command:
wvs flow set flavor <FLOW_NAME> <FLAVOR>
Replace the following:
<FLOW_NAME>with the name of the flow.
<FLAVOR>with a descriptive, case-sensitive string. We recommend not adding spaces or special characters.
Using our previous example, you want to group the outputs of the
myBuild1 flow as
QA and the outputs of
myBuild2 flow as
execReview. To you this, you run the following command:
wvs flow set flavor myBuild1 QA wvs flow set flavor myBuild2 execReview
Now, in the Builds Browser of the WVS Web Client, all
myBuild1 outputs are grouped together under
myBuild2 outputs are grouped together under
- Learn where to view and download flow output.
- Learn how to configure the flows in your project.
- Learn how to enable for disable the flows in your project.
- Learn how to add flows to your project.
- Learn how to get information about project flows.
- Learn how to validate the configuration of your project flows.