Skip to content

Deployment and CI/CD Updated 2026-05-27

Deployment Manager

The Deployment Manager panel — where application archives and Git/SVN repositories are registered for reuse across environments on Stack Harbor PaaS.

The Deployment Manager is the panel at the bottom of the dashboard that stores reusable deployment sources — application archives and registered Git/SVN repositories. Anything stored here can be deployed to any compatible environment without re-uploading or re-registering it.

Two tabs cover the two source types:

  • Archive — application packages uploaded from a local file or fetched from a URL.
  • Git / SVN — registered VCS projects, with optional access credentials.

Archive tab

The Archive tab lists every uploaded archive in your account:

  • Name — the archive file name.
  • Comment — optional note describing the application.
  • Size — archive size.
  • Upload Date — when the archive was added.

Uploading an archive

Click Upload. The dialog accepts two upload modes:

  • Local file — pick a file from your local machine. Maximum size: 150 MB.
  • URL — supply a public URL pointing to the archive. Use this mode when the archive exceeds the 150 MB limit.

Optionally fill in the Comment field, then click Upload.

Deploying an archive

Hover over the archive entry and click Deploy to. The deploy dialog opens with the archive pre-selected. Configure the target environment, path, hooks, and deploy strategy, then click Deploy.

Removing archives

Select archives via their checkboxes and click Delete in the top panel.

Git / SVN tab

The Git / SVN tab stores references to remote repositories along with access credentials. Once a repository is registered, it can be deployed to any environment.

Registering a repository

Click Add Repo. The dialog requires:

  • Name — project name. No spaces or special characters.
  • Type — Git or SVN.

For Git:

  • URL — repository URL.
  • Branch — branch to track (defaults to master).
  • Use Authentication — optional. Supports password, token, or SSH key authentication.

If the repository is protected with two-factor authentication, use a personal access token from GitHub, GitLab, or your VCS provider — not your account password. Token scopes should be limited to the minimum required by the deployment workflow.

For SVN:

  • URL — repository URL.
  • Login and Password — authentication credentials (if the repository requires them).

Two action buttons are available:

  • Add — register the project in the Deployment Manager without deploying.
  • Add + Deploy — register and immediately open the deploy dialog.

Managing registered repositories

Hover over a Git / SVN project entry and use:

  • Deploy to — open the deploy dialog with the repository pre-selected.
  • Edit — change name, URL, branch, or credentials.
  • Delete — remove the registration. Already-deployed projects on application servers are not affected.

Credential rotation

When a repository’s credentials change — for example, a rotated personal access token — update them once in the Deployment Manager. The platform then prompts to apply the new credentials to each existing project that uses the repository. Confirm to update.

See also