Code source
Connect the project to a repository on GitHub, Azure DevOps, GitLab or Bitbucket, or use .zip upload, and choose the Production and Preview branches.
Code source
The code source decides where the project gets its code from on every deploy. It is set in the project's settings, on the Repository tab, under Deployment mechanism:
| Mechanism | How deploys happen |
|---|---|
| GitHub | On every push to the configured branch. |
| Azure DevOps | On every push to Azure Repos. |
| GitLab | On every push to GitLab. |
| Bitbucket | On every push to Bitbucket. |
| .zip file | On every manual upload of a new version, Production only. See Deployments. |
To connect a Git provider, click Connect with {provider}. Roberty only reaches the repositories you authorize, and you can disconnect at any time. There is no connection by personal token (PAT, app password or project token): authorization always goes through signing in to the provider.
GitHub
- Install the Roberty GitHub App on your GitHub account or organization.
- Authorize access to the repositories you want. When you finish, you are taken back to the project.
- Choose the repository and each environment's branch.
If the app is already installed on more than one account, choose the account — Organization or Personal — or use Connect another account to install it on another one. Pushes arrive through the app itself: there is nothing to configure in the repository.
Azure DevOps
- Click Connect with Azure DevOps and sign in with the organization's Microsoft account (a Microsoft Entra ID work account).
- If the account belongs to more than one Azure DevOps organization, choose the one that holds the repository.
- Choose the repository and the branches. The list holds the repositories of every project in the organization.
When you save, Roberty creates a Code pushed Service Hook in the Azure DevOps project on its own.
Requirements and limits:
- Personal Microsoft accounts (Outlook, Hotmail, Live) are not supported: the organization must be backed by a Microsoft Entra ID directory.
- Administrator approval required: if the company's directory doesn't let users approve applications, the connection screen shows an approval link. Open it, or copy it to a Microsoft Entra administrator, who approves Roberty once for the organization; then connect again.
- Only Azure DevOps Services is supported — Azure DevOps Server (on-premises) and TFVC repositories are not.
- Conditional access policies that enforce IP rules on non-interactive flows too may block Roberty's calls. If that happens, contact support.
- If the authorization is canceled, the account belongs to no organization, or the connection link expires, the screen shows the reason and lets you try again.
Disconnect removes the Service Hook Roberty created. To also revoke the application's consent, remove Roberty at myapps.microsoft.com.
GitLab
- Click Connect with GitLab, sign in with your gitlab.com account and authorize the Roberty Code application.
- Choose the repository and the branches. The list holds the non-archived projects your account is a member of, personal and group ones.
When you save, Roberty creates a push webhook in the GitLab project on its own.
Requirements and limits:
- gitlab.com only — GitLab self-managed and GitLab Dedicated are not supported.
- For Roberty to create the webhook, your account needs the Maintainer or Owner role on the project. With a lower role the connection works, but the webhook has to be set up by hand.
Disconnect removes the webhook Roberty created and revokes the application's access.
Bitbucket
- Click Connect with Bitbucket and sign in with your bitbucket.org account.
- If the account belongs to more than one Bitbucket workspace, choose the one that holds the repository.
- Choose the repository and the branches. The list holds the chosen workspace's repositories.
When you save, Roberty creates a Repository push webhook in the repository on its own.
Requirements and limits:
- Bitbucket Cloud only — Bitbucket Data Center and Bitbucket Server are not supported.
- One workspace per project. To use a repository from another workspace, disconnect and connect again, choosing the other workspace.
- For Roberty to create the webhook, your account must be a repository admin. Without that permission the connection works, but the webhook has to be set up by hand.
Disconnect removes the webhook Roberty created. To also revoke the application's access, remove Roberty Code under Personal settings → App authorizations in Bitbucket.
Repository and branches
With the provider connected, choose where each environment's code is synced from:
| Field | Required | Description |
|---|---|---|
| Repository | Yes | Search among the repositories available on the provider. |
| Production | Yes | The branch deployed to the Production devices. |
| Preview | No | The test branch, deployed to the Preview device. |
The same branch cannot be used for both environments. When you save, the repository and branches apply to the next deploys. From then on, every push to one of these branches deploys to the matching environment's devices.
The connected account's card shows Active connection or Reconnection required.
Webhook
On Azure DevOps, GitLab and Bitbucket, pushes arrive through a webhook that Roberty tries to create when you save the settings. The Webhook panel shows its state:
| State | What it means |
|---|---|
| Active | Automatic deploy is on: every push to the configured branches deploys. Shows the date of the last push received. |
| Manual setup | Your account is not allowed to create the webhook. The panel shows the URL and the secret ready to copy, and someone with permission follows the steps below once. |
| Failed | The webhook was not created. Pushes won't deploy until this is resolved. Use Try again. |
Manual setup steps:
- Azure DevOps (project administrator): Project settings → Service hooks → +, choose Web Hooks and the Code pushed event, select the repository (leave Branch and Pushed by as [Any]), paste the URL and the header into HTTP headers and finish.
- GitLab (project Maintainer): Settings → Webhooks → Add new webhook, paste the URL and the Signing token, check only Push events under Trigger and save.
- Bitbucket (repository admin): Repository settings → Webhooks → Add webhook, paste the URL and the Secret, keep only Repository push under Triggers and save.
Then use Check again. The first push received also marks the webhook as active.
Reconnecting
On Azure DevOps, GitLab and Bitbucket, the authorization can expire or be revoked (a password change, a directory policy, a removed account). When that happens, the project shows Reconnect {provider} and pushes don't deploy until you reconnect. The repository and branches are locked for editing until then.
Reconnecting with the same account — and, on Azure DevOps and Bitbucket, the same organization or workspace — keeps the repository, branches and webhook configured. Choosing another Bitbucket workspace counts as a new connection.
Switching provider
Switch provider disconnects the current provider so you can connect another one:
- The current provider's connection is removed from the project.
- Devices stop running and stay without code until you connect the new provider and pick a repository and branches.
- The platform does not copy the code: moving the repository to the new provider is up to you.
- The deployment history is kept, but rollback is only available for deployments from the connected provider.
Switching between Git and .zip
The deployment mechanism can be switched between a Git repository and .zip upload. You can't switch while a deploy is in progress.
From Git to .zip:
- The Git provider connection is removed from the project.
- The Preview device is unlinked and its schedules are deleted.
- Production devices stop running and stay without code until the first .zip upload.
From .zip to Git:
- The .zip file is deleted from the platform and its space is returned to the workspace.
- Devices stop running and stay without code until you connect a Git provider and pick a repository and branch.
Either way, the deployment history is kept but past versions cannot be redeployed, and moving the code to the new source is up to you.
Permissions
Only workspace administrators can disconnect the provider, switch provider and switch the deployment mechanism.