Why and when we need to use CI/CD pipelines in UiPath?

Hi all,

What is the purpose of using CI/CD pipeline in UiPath??

When we need to use this.

Thank you in advance

@naveen.s,

The purpose of using CI/CD pipelines within UiPath or any development is to enable faster and more predictable automation development & deployment.

An example by LLM:

Sample CI/CD Pipeline in UiPath using Azure DevOps Pipelines

Step-by-Step Guide

  1. Set up an Azure DevOps Organization
  • Sign up for or log in to the Azure DevOps portal.
  • Create a new project.
  1. Integrate UiPath Extension into Azure DevOps
  • Navigate to Organization Settings.
  • Go to the Extensions tab.
  • Search for UiPath in the Visual Studio Marketplace and install the UiPath Integration extension.
  1. Create a New Project in Azure DevOps
  • Click on the New Project button on the Azure DevOps home page.
  • Provide a name and description for the project, then create it.
  1. Connect UiPath Orchestrator to Azure Project
  • Create an External Application in UiPath.
  • Obtain App ID and App Secret and set up a Service Connection in Azure DevOps using these credentials.
  1. Set up a Git Repository in Azure DevOps
  • Navigate to Repos in the Azure DevOps project.
  • Generate Git credentials and add your UiPath project to Git.
  • Commit and push your UiPath project to the Azure Repo.
  1. Create a Build Pipeline
  • Go to Pipelines in Azure DevOps and create a new pipeline.
  • Connect the pipeline to the Azure Repo.
  • Add tasks to the pipeline for:
    • Packing the project into a NuGet package.
    • Executing test cases in UiPath Orchestrator.
    • Creating an artifact for the release pipeline.
  1. Create a Release Pipeline
  • Navigate to Releases in Azure DevOps and create a new pipeline.
  • Add an artifact linked to the build pipeline.
  • Add tasks to deploy the package to UiPath Orchestrator.
  • Set up Continuous Deployment triggers.

YAML Configuration Example

# Template: Starter Pipeline
trigger:
- main

pool:
  vmImage: 'windows-latest'

steps:
- task: UiPathPack@2
  inputs:
    versioningMethod: 'Patch'
    traceLevel: 'Verbose'
    projectPath: '$(Build.SourcesDirectory)'
    outputPath: '$(Build.ArtifactStagingDirectory)\\Output'

- task: UiPathTest@2
  inputs:
    testSetMethod: 'ExecuteTests'
    orchConnection: '<orchestrator-service-connection>'
    folderPath: '<folder-path>'
    testSetName: '<test-set-name>'

- task: PublishBuildArtifacts@1
  inputs:
    pathToPublish: '$(Build.ArtifactStagingDirectory)'
    artifactName: 'drop'
    publishLocation: 'Container'

This setup demonstrates a basic CI/CD pipeline for a UiPath project using Azure DevOps.

From Documentation:
Continuous integration / continuous deployment refers to a practice that enables a faster and predictable automation development.

You can start from here:

1 Like

Hi @naveen.s ,
A CI/CD pipeline in UiPath helps automate the process of developing, testing, and deploying RPA projects. It ensures:

Faster Development – Multiple developers can work together without conflicts.
Automated Testing – Detects bugs early and ensures high-quality bots.
Quick Deployment – Moves projects smoothly from development to production.
Fewer Errors – Reduces manual mistakes and improves reliability.
Version Control – Tracks changes and allows easy rollback if needed.

Regards,
Arivu

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.