Skip to main content
Roberty Studio
CODECode

Deployments

Follow each device's deployment history, retry a deployment, roll back and publish new versions by .zip upload.

Deployments

A deployment takes a version of the code to the project's devices. On every deployment, Roberty validates the project's structure (see Preparing the project), installs the dependencies and leaves the code ready to run on the device.

What triggers a deployment​

  • Git project: a push to the branch configured for an environment deploys to that environment's devices — the Production branch to the Production devices, the Preview branch to the Preview device. See Code source.
  • .zip project: each upload of a new file deploys to the Production devices. See .zip upload.

While there is no deployment yet, the Deployments tab points to the first step: "Push the first commit to the configured branch to get started" (Git) or "Upload the project .zip to get started" (.zip).

History per device​

Every deployment is recorded per device. The Deployments tab shows one tab per linked device — Production devices first, then the Preview one — with that device's history. With no linked devices, there is no history to list.

Search by branch, reference, repository or ID. The list is paginated, 20 deployments per page.

Each row shows:

  • the deployment's branch or reference and the environment;
  • the source and, in Git projects, the short commit with its message;
  • the Does not run in parallel badge, when that deployment's roberty.json has "blockParallel": true — the project runs alone on the device, and RPA robots and other code projects wait for it to finish (see Preparing the project);
  • the status and the date.
StatusMeaning
ActiveThe deployment in use on the device — the one runs use.
SuccessThe deployment finished successfully, but is not the one in use.
PendingThe deployment hasn't started yet.
In progressThe deployment is being applied.
FailedThe deployment did not complete.

Details and logs​

Click a deployment to open its details: reference, repository, whether it is the active deployment, and the deployment logs — useful to understand a validation or dependency-install failure.

Retry and rollback​

ActionWhere it appearsWhat it does
RetryOn the active deploymentRe-applies the deployment on the selected device only.
RollbackOn earlier deploymentsGoes back to that version. In Production, the deployment is re-applied on all Production devices; in Preview, on the Preview device.

Both actions ask for confirmation and are not available for:

  • .zip deployments;
  • deployments from a provider other than the one connected now;
  • deployments in progress;
  • failed deployments that are not the active one.

.zip upload​

In projects that receive code by .zip, new versions are published with the Upload .zip (Production) button on the Deployments tab.

  • The file must be a non-empty .zip of up to 100 MB.
  • Each upload replaces the previous one and deploys to the Production devices.
  • If the file is identical to the current one, no deployment is triggered.
  • If a deployment is already in progress, wait for it to finish and upload again.
  • The file counts toward the workspace's storage limit. If the limit is reached, free up space or ask an administrator to raise it.
  • .zip projects have no Preview and no rollback.

Notifications​

While the project is open, notices follow each deployment: when it starts running, when it succeeds and when it fails, naming the device — or the number of devices, when the deployment reaches several at once.