Auto-Deploy Overview

Auto-Deploy of Git/SVN Updates

Auto-deploy periodically checks a connected Git or SVN repository and updates the deployed application whenever new commits are detected.

The feature supports a standard version-control workflow without requiring a manual deployment after every commit or repository-side webhook configuration.

Git and SVNWorks with registered Git and Subversion repositories.
Scheduled ChecksChecks the selected branch at a configurable interval.
Automatic UpdatesStarts deployment only when new code is found.
No Repository HookDoes not require Git-side or SVN-side webhook setup.
On this page

How Auto-Deploy Works

After a repository project is connected to an environment, the platform checks the selected branch at the configured interval. When a new commit is found, the application is rebuilt or updated automatically.

  • Java projects can be rebuilt through Maven and then deployed.
  • PHP and similar interpreted projects are updated directly.
  • No deployment starts when the repository has no new changes.

Configure Auto-Deploy

1Create the target environment

Prepare the application server, build node, database, and other services needed by the project.

2Add the repository project

Click Add Project for the application server or Maven node, or register the repository through Deployment Manager.

3Enter repository details

Select Git or SVN and provide the project name, repository URL, branch or path, target context, and authentication details when required.

4Enable automatic updates

Select Check and auto-deploy updates, define the check interval in minutes, and save the project.

Auto-Deploy Options

  • Check every: Determines how often the repository is checked.
  • Checkout now: Deploys the project immediately after adding it.
  • Auto resolve conflict: Replaces conflicting local files with the repository version.
  • Zero-downtime deployment: May be available for selected stacks and deployment types.
Conflict handling: Keep automatic conflict resolution enabled unless you intentionally maintain local changes inside the deployed project and understand the consequences.

Edit or Disable Auto-Deploy

Hover over the connected project and click Edit. Update the repository URL, branch, authentication, interval, or deployment options. Clear Check and auto-deploy updates to disable automatic checks.

Check Deployment Logs

  • For Java projects, review the Maven VCS update log.
  • For PHP and application-server projects, review the Git or SVN update log.
  • Use the Tasks panel to track active or queued deployment operations.

Important Considerations

  • Choose an interval that is longer than the normal build and deployment duration.
  • If a new check occurs while deployment is running, the next task waits in the queue.
  • For multi-node application layers, updates can be applied sequentially to reduce downtime.
  • Repository credentials or access tokens should use the minimum required permissions.
  • Use a push-triggered deployment tool when immediate deployment is required.
Auto-deploy is best suited to workflows where a small polling delay is acceptable and the repository contains code that can be deployed directly or built by the platform.

What’s next?

  • Git & SVN Auto-Deploy for Multiple Containers
  • Deployment Manager
  • Git-Push-Deploy
  • Deployment Guide