Azure DevOps Repos for UiPath Robots

Is creating one repository for each robot/process in Azure DevOps better than having one repository for all the robots?
If yes, then why?
Will it have any impact in Pipelines (when we build)?

@Arun_Kumar_Punjabi

Welcome to the community

  1. When you have 1 repo for 1 process then we will make the repo very high…but advantage is we can set a trigger whenever new code is pushed in the build pipeline
  2. When you have one repo and all processes under it…then you cannot set the trigger on repo as it will contain all processes…so in build you have to select the process it needs to deploy…work around for this would be may be you can create one build for each process inside the branch as well.

Hope this helps

Cheers

1 Like

Hi @Arun_Kumar_Punjabi

In general, it is generally recommended to create one repository for each robot/process in Azure DevOps, rather than having one repository for all the robots. This is because having separate repositories allows you to manage and version control each process independently, which can make it easier to maintain and update your processes over time.

Having separate repositories for each process can also make it easier to build and deploy your processes using Azure DevOps pipelines. When you build a pipeline for a specific process, you only need to include the relevant files and resources from the corresponding repository, rather than having to include all the files and resources from a single, large repository. This can make it easier to manage the build process and reduce the risk of conflicts or errors.

In terms of the impact on pipelines, having separate repositories for each process can make it easier to build and deploy your processes in a consistent and reliable way.

Thanks!!!

1 Like