Deploying a pipeline
Once the pipeline flow has been created, the next step is to make it available for use, that is, deploy it. On the Run tab, you can deploy your pipeline in seconds, depending on the size of your deployment. This deployment can be done both in the test environment (test) and in the production environment (prod).
If you want to know more about the Run step, where deployments are managed, see the article Run concepts.
To have access to Deployment, you must have been assigned the Deployment (test/ prod): Read and Create role for your user account or a group to which you belong.
The process to deploy the pipeline to a test or production environment is simple. Follow these steps:
Access the Run screen and click the + CREATE button.

Select a pipeline and its version. After you select the pipeline, information about the project it belongs to and the instance, if it is a multi-instance pipeline, is displayed. Then select the desired pipeline size. If it is a multi-instance pipeline, select an instance as well.
Important: Archived pipelines are a minor version of a pipeline that is no longer active and are not available for deployment. To learn more about pipeline versions, read this article.
The configuration options are displayed as in the example below:

If the pipeline is already deployed, a section is displayed informing the current deployment configuration, which is automatically applied to the new deployment. To learn more about the status of pipeline deployment, read this article.
Also in this section, it is possible to visit the pipeline currently deployed through the link Open the pipeline in a new tab.

Select the number of concurrent executions, as in the example:

Define the number of replicas to be used.

If the pipeline has been previously deployed, a message will appear just below the replica selection.
Click on the DEPLOY button. Clicking the DEPLOY button will display a summary of all selections made. After you click Deploy, the screen will redirect to the project the pipeline belongs to, so you can track the pipeline.
For Pipeline Based Model users, the system will be displayed a screen with the calculation of licenses consumed for deployment.

For Subscription Based Model users, the system will be displayed a screen with the calculation of RTUs and subscriptions.
Note that as of 04/01/2022 we have adopted a new implementation control and pricing model, so there is a confirmation screen with new information. Learn more about the Subscription Based Model.

We would like to hear your comments and suggestions on this feature. See how easy it is to send your feedback:

Last modified 3d ago