We are working on a number of UIPath bots. For the longest time, we’ve been publishing our processes to our DEV Orchestrator using UIPath Studio. We have finally been given our QA environment and we need to migrate our process to QA and test them there. I’ve run into a problem with synching libraries between the two Orchestrators.
I don’t know if this is the proper way to do it, but this is what I’ve been doing:
develop the process
test locally
publish to DEV
test attended and unattended in DEV
download the bot’s package and locally developed library packages
upload to QA
That is doable but has a high PITA factor. The problem I’m running into is, it looks like the only UIPath libraries in QA are the latest ones that were available when Orchestrator was installed in that environment. In this case, that was 3 months ago, but I have updated my bots to use later versions of the UIPath libraries.
Am I doing this the right way? How do others sync bots and libraries between different Orchestrator instances (installed on different “machines”)? This is just the first step because we will eventually get our Production environment and will had to then sync everything to it.
As @ppr pointed out I too suggest the DevOps route will solve most of your challenges. Investing in DevOps is essential when your team is scaling up automations / or number of developers in the team. More commits, more environments, more hassle!
From our team analysis, we save about 5 to 10 minutes for each publishable commit to our two orchestrator instances (due to the need of logging into 2 different secure VMs). In other words, as you scale your automation team/effort, DevOps is not a nice to have, it will be a must.
Please go through these threads / repository on how you can use DevOps to find a solution to your query.
You don’t need to put all the libraries into Orchestrator. The robots download them automatically and install them locally on the server they’re running on.