Need full procedure about deployment

Help Orchestrator
1

Hi,

I want the end to end procedure of deployment of various scenarios.(attended, unattended, prod, test, dev environment transitions etc.)

Thanks.

2

Hi,
End-to-end deployment depends on the setup, but in general:

  • Dev → build & test in Studio.
  • Test → publish to Orchestrator, validate with test robots.
  • Prod → deploy package to Production folder, connect attended/unattended robots.
  • Attended → users trigger from Assistant.
  • Unattended → jobs scheduled/triggered in Orchestrator.

For detailed steps, you can check UiPath official docs — they cover each scenario with best practices. Orchestrator

3

Hello @ADITYA_T
Here is the explanation in simple term
Development:
Build the automation in UiPath Studio.
Test it on your machine, connected to a Dev Orchestrator.
Testing:
Move the working project to a Test Orchestrator.
Run it using a dedicated test robot to confirm it works correctly in a separate environment.

Production:
Deploy the final, approved version to the Production Orchestrator.
Run it using unattended robots on live servers to handle real business tasks.

Attended: The user starts the robot on their PC.
Unattended: Orchestrator starts the robot on a dedicated server.

4

Hi @Michael.Vornes @asadali.shaikh

How to deploy the package and how to move the packages to different Environments(PROD,TEST,DEV).

5

Hi @ADITYA_T

You can consider below approach:

  1. I assume you must be publishing packages to dev using your UiPath studio, if not you must be doing via uploading a package and then creating/upgrading the process on orchestrator.

  2. for UAT, we manually upload package on orchestrator, set up the environment for process run. Then we schedule uat demo, once approved, we freeze the package version.

  3. then we raise change request via service first for production implementation. And manually upload the package again. Now here, if developers are allowed to promote packages to prod, they can do so and then your process owner can verify the version number post which PO can upgrade the process for run or create a trigger for same. If developers don’t have access for package deployment on prod, then PO itself is responsible for uploading the package and then upgrading the process.

Hope this helps.

6

The processo to deploy and move the package to different environments will depend on the procedures your organization adopts.

You can have for example a very simple process where you will publish the package locally (you select that option when you will publish from your studio), then you can import the package in Dev Environment and test, if it is working fine you can use the same package and import to QA and PROD. But this is the simpliest way.

Gerenally companies adopt more robust processes, like the developer publish directly to the Dev Orchestrator and the you can use GitHub and commit the project there, and you can have a pipeline in some other environment like azure devops, that will publish to QA, you can also can configure Pull Requests to publish to PROD.

So it really depends on the process your company adopts. I would suggest you to search for CI CD process, then you will undertand better how a CI CD process works, it is used not only for UiPath but for any kind o development and deployment :slight_smile:

If you think it was helpful please mark as the solution :slight_smile: