Banner background image
Studio User Guide
Last updated Dec 20, 2023

About Publishing Automation Projects

Publishing an automation project means archiving the project folder so that it can be sent to Robots and then executed.

By default, all the files in the project folder are published. If you want to prevent a specific file from being included in the published package, right-click it in the Project panel, and then select Ignore from Publish. In the case of libraries, ignoring a workflow file from publish prevents it from appearing as a reusable component in the Activities panel when the published library is installed in a project.

You can publish automation projects to Orchestrator, a custom NuGet feed, or locally. After publishing to Orchestrator, the archived project is displayed on the Packages page and you can create a process to be distributed to Robots. When you publish an automation process to the Orchestrator Personal Workspace or you publish test cases, a process is created automatically if one does not already exist, and existing processes are automatically updated to the latest published version.

Additionally, automation projects may be published to a custom NuGet feed, with the option to also add an API key if the feed requires authentication.

Publishing projects locally requires you to provide a path on the local machine, different than the location where process packages are published. From here, you can later manually send the packages to the Robots, so they can be executed. The default local publish location is %ProgramData%\\UiPath\\Packages.

You can publish projects from Studio or from the command line. To update dependencies for multiple projects and publish them all at once, use the Project Dependencies Mass Update Tool.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.