UiPath Devops.pptx

Editor's Notes

• #5 Continuous Integration (CI) Continuous integration (CI) is the practice used by development teams to simplify the testing and building of code. CI helps to catch bugs or problems early in the development cycle, which makes them easier and faster to fix. Automated tests and builds are run as part of the CI process. The process can run on a set schedule, whenever code is pushed, or both. Items known as artefacts are produced from CI systems. They’re used by the continuous delivery release pipelines to drive automatic deployments. Continuous Delivery (CD) Continuous delivery (CD) is a process by which code is built, tested, and deployed to one or more test and production stages. Deploying and testing in multiple stages helps drive quality.  Continuous integration systems produce deployable artifacts which are used in CD to release new versions and fixes to existing systems. This process ensures that errors are caught often and early.
• #6 Let’s quickly discuss the key concepts used in the azure pipeline. An Agent is computing infrastructure with installed agent software that runs one job at a time. You can treat the agent as executor which actually performs the jobs as instructed by the pipeline stages. Your agent must have the capability to perform a certain action. In our example, UiPath must be installed on an agent to perform build/test. A trigger tells a Pipeline to run. In the above example, It’s the setup that tells when the pipeline needs to be run. You can configure a pipeline to run when you publish your UiPath Projects to Git or Repo you are using. This can be also configured to run at scheduled times or upon completion of another build. A Stage is a logical grouping of Jobs in the pipeline and each stage can have one or more jobs that run on Further your job can contain one or more step(task/script) A Step can be a task or script and is the smallest building block of a pipeline. For example, you are creating a pipeline which consists of build and test steps both. Your step can be either a ‘task’ [Custom Code] Or Script written in PowerShell or Shell Script. For example, there is a task, that task has got five different stages, and each stage has got some steps. All the steps in phase one have to be completed, to mark the latter stage to be complete. 
• #7 CI/CD in Context of RPA Tool UiPath Although many organizations have started implementing a Digital Workforce into their business operations – only a few are fully in control of their RPA bots. Very few COE has already implemented the CI/CD (Continuous Integration, Continuous Delivery) pipeline that allows you to automate your robot delivery process. A typical pipeline for UiPath can be – The pipeline will initiate the build from your version control system. The pipeline will also perform the creation of various assets, config replacement, creating initial folders etc. The pipelines will publish the package to Orchestrator. It can further include workflow analyzer to code review, approval workflow, integration with ITIL tools such as(service now) for change board approvals. It can be further improved to Run test cases from Orchestrator.
• #8 Task execution must be perfomed on a Windows-based build agent Orchestrator instance (basic, federated or cloud authentication are supported) Testing features require Orchestrator version 20.4 or newer When using an on-premise Orchestrator under HTTPS, make sure to import the SSL Certificate so that the HTTPS calls to Orchestrator can be trusted
• #10 You can skip this slide and move directly to the demo, if needed but make sure you have filled in the previous slide in which you explain the purpose and steps of the demo.
• #11 To add an Orchestrator Service Connection (based on the tenant) In the Azure DevOps project, click on Project Settings on the bottom left of the page. Click on Service connections under Pipelines. On the top right of the page, click New service connection. Choose UiPath Orchestrator Connection as the type and click next. For on-premise Orchestrators, you will be using Basic Authentication with a username and password. Specify the Orchestrator URL and tenant as well. Name the connection (it is a good idea to include the environment and tenant in the name) then click save. To add variables to store client id/user key etc. In the Azure DevOps project, click on Project Settings on the bottom left of the page. Click on Library under Pipelines. On the top of the page, click + Variable Group. for this example, we have given group name as “UiPath” You can now add all the variables you need inside the pipeline. (for our use case we need Orchastarator API Details so so that we can publish the package to the different environment ) For reusability, you should create different groups for different environment and projects. this will help to restrict the usages.
• #12 You can skip this slide and move directly to the demo, if needed but make sure you have filled in the previous slide in which you explain the purpose and steps of the demo.