9. CI/CD Pipelines for UiPath Process Deployment
Series: Azure DevOps
UiPath Kerala Chapter
UiPath Chennai Chapter
10. Introduction to Azure DevOps and CI/CD Pipelines 15 mins
Setting Up Your UiPath Environment with Azure DevOps 20 mins
Building CI/CD Pipelines for UiPath Automation 20 mins
Demo 20 mins
Q&A and Open Discussions 15 mins
11. What is CI/CD…?
Continuous integration and continuous delivery (CI/CD) is a software development approach where all developers
work together on a shared repository of code – and as changes are made, there are automated build process for
detecting code issues. The outcome is a faster development life cycle and a lower error rate.
Azure CI/CD refers to the practice of Continuous Integration and Continuous Deployment, which are key components
of the software development lifecycle. CI/CD helps automate and streamline the process of building, testing, and
deploying applications, resulting in faster and more reliable software releases.
12. What is CI/CD in Context of RPA Tool UiPath?
A standard UiPath workflow may involve the following steps:
• Commencing the build process from your version control system through the pipeline.
• Executing tasks like asset creation, configuration replacement, and initial folder creation within the pipeline.
• Publishing the package to Orchestrator as part of the pipeline workflow.
• Enhancements can be made by incorporating elements like workflow analyzer for code review, an approval workflow, and
integration with ITIL tools like ServiceNow for change board approvals.
• Continuous improvement may involve running test cases directly from Orchestrator.
13. 13
The key components and stages of an Azure
Pipeline include:
Pipeline Definition: This is where you define the structure and stages of your pipeline. Depending on your
preference, you can create a pipeline using either YAML or the visual designer.
Agents: These are the execution environments where your pipeline jobs run. Azure Pipelines supports both
Microsoft-hosted agents and self-hosted agents.
Trigger: Triggers determine when the pipeline should be executed. You can set up various triggers, such as
manual, scheduled, or triggers based on code changes (e.g., pull requests, branch updates
Jobs: Each stage consists of one or more jobs. A job represents a unit of work that can be executed on an
agent. Jobs can include multiple steps, scripts, and tasks that need to be completed.
Stages: Stages represent logical divisions within your pipeline. Each stage typically corresponds to a specific
phase in your CI/CD process, such as building, testing, and deploying.
Steps: Steps are individual tasks that make up a job. Each step performs a specific action, such as checking
out source code, running a script, or deploying artefacts.
Artifacts: Artifacts are built outputs or files produced during the build process and can be used in
subsequent stages or jobs. Artefacts can include compiled code, binaries, configuration files, and more.
14. 14
Different ways to define Azure Pipeline
Defining Azure Pipelines in YAML:
Defining Azure Pipelines using the Interface:
