The Workspace ONE Delivery Pipeline allows admins to automate the delivery of these items between the different environments and reduce the number of human touches. Additionally, this would enable them to create a phased (ring) approach to delivering the items in production and test groups.
- Decreases the time to deploy an item to other organization groups or environments with a button click.
- An innovative approach to promoting an item to production users that reduces human error and effort.
- Easily visualize a phased (ring) deployment of a profile, baseline, script, sensor, etc.
To create a new pipeline, perform the following actions:
- Click the Add button.
- On the dialog that opens enter the Pipeline Name, Select the targeted platform and the pipeline type.
- Click Save
The dialog will dismiss and the pipeline name will show on the screen now. To edit and view the details of the pipeline, click the pipeline name to navigate to the detail screen.
Each step of a pipeline determines how the resource will be handled for the environment of a step. When a step is created, a description/name is added, a target environment is configured, and optionally, the step can be linked to an existing item.
Create a Step
To create a step then:
- Click the Add Step button
- Provide a Name, Description (Optional), Target Environment, and optionally select an existing resource.
- Click Save to add the step to the pipeline.
The step will now be linked with the other steps in the pipeline. To edit the details of a step or delete the step, then click the Details button next to the step.
To take action with a pipeline, the active step needs to be executed. Executing a step results in the following behavior depending on which step is being excuted.
The first step is crucial for a pipeline. This step should be linked to the resource that is created or modified with new changes. The first step, pulls the resource data into the pipeline. Each subsequent step will use the data pulled from the first step in order to create or update resources.
Each step after the first behaves the same way. If the step is linked to a resource, then the step will update that resource with the data from the first step. If the step is not currently linked to a resource, then it will create a new resource in the target environment.
Once the pipeline retrieves the resource data, a data view displays to the right of the pipeline. This happens after the first step is executed and is updated once the first step is run again.
The view will show basic resource information and also an overview of the resource data itself.
Additionally, toggling the show differences view will show what is different between the current active step and the pipeline's resource data.
To run through the pipeline again, then click the reset button. The reset button will set the current step to be the first step again so that each step can be executed in order. Typically this would be when the resource has changed and needs to be executed again.