UPVALE / GUIDES

Repositories

Connect GitHub, GitLab, or Bitbucket Cloud once and reuse the connection for application builds.

On this page

Open Repositories directly below Registries in the sidebar. A repository connection gives applications in the active Upvale organization access to a Git provider's repositories. You select the connection, repository, and branch when configuring an application.

Viewing connections requires Manage infrastructure or Manage workloads. Adding or removing a connection requires Manage infrastructure. Building and deploying an application requires Manage workloads and Manage deployments.

Connect an account

  1. Open Repositories → New connection.
  2. Choose GitHub, GitLab, or Bitbucket Cloud.
  3. Select Connect, then complete authorization with the provider.
  4. Return to Upvale. The connection appears with its provider, account, and creation date.

Connections support GitHub.com, GitLab.com, and Bitbucket Cloud. Bitbucket workspaces are listed through the connected account; no separate workspace connection is needed.

For GitHub, choose the account and repositories available to the GitHub App, then authorize access. GitLab and Bitbucket Cloud use their account authorization flows. Each provider must first be configured by your administrator; unavailable providers are marked not configured.

Connections belong to the Upvale organization where you started authorization. Switch organizations before connecting an account intended for another team.

Use a connection in an application

  1. Create an application or open Application → Source on an existing one.
  2. Choose Git repository.
  3. Select a Repository connection, then choose its Repository and Branch.
  4. Select a Build node. Upvale manages image storage automatically.
  5. Set the Dockerfile path. The defaults use Dockerfile in the repository root with build context ..
  6. Choose whether to Deploy on push.

GitLab and Bitbucket Cloud need permission to create a repository webhook when Deploy on push is enabled. Leave this option off when you want manual builds without webhook-management access.

Creating a Git application queues its first build. For an existing application, select Save source, then Build and deploy. Track the commit, build logs, cancellation, and deployment in Deployments. See Applications for all build settings.

To store build images in an external container registry, enable Advanced build settings → Use my own registry. Select a registry with push access and enter the image repository. This registry connection uses separate credentials from your Git connection.

Remove a connection

Select Remove beside an unused connection and confirm. If an application still uses it, change that application's source to another connection or to a container image first.

Removing a saved connection does not delete the repository or the application's build history. Provider-side app authorizations are managed in the provider's account settings.