Automatically Build on Git Push

CloudStation can automatically build and deploy your application whenever you push changes to your Git repository. This feature keeps your application up to date without manual intervention, streamlining your development workflow.

How It Works

When Automatic Build is enabled in your project settings, CloudStation follows these steps after every Git push:

1. Detect Changes – CloudStation detects the update in your repository.
2. Start Build – A build process begins using the specified Build Context (default: /).
   • If a Dockerfile is present, it will be used for the build.
   • If no Dockerfile is found, CloudStation defaults to the Nixpacks builder.
   • For more details, check the [Builders Documentation].
3. Execute Build – The build runs based on the detected configuration.
4. Deploy or Push to Registry – Once the build is complete, CloudStation takes one of the following actions based on your deployment settings:
   • Build and Deploy – Instantly deploys the new build.
   • Build and Push to Registry – Stores the build in a container registry.
   • Build, Push, and Deploy – Pushes the build to a registry and then deploys it.
   • For private registry configurations, see the [Private Registry Documentation].

If Automatic Build Is Disabled

When Automatic Build is turned off, you must manually trigger builds from the CloudStation UI. This gives you greater control over when and how deployments occur. Common use cases include:

• Controlled Deployments – Review and test changes before deploying.
• Selective Builds – Deploy only specific changes instead of every push.
• Scheduled Releases – Deploy updates at planned times rather than immediately.

How to Manually Trigger a Build

1. Open Your Project – Navigate to your project in the CloudStation dashboard.
2. Start the Build – Go to Settings and click the Deploy Changes button.

Deployment Options

• Build and Deploy – Automatically deploys the new version after a successful build.
• Build and Push to Registry – Saves the new build to a configured registry.
• Build, Push, and Deploy – Pushes the build to a registry and deploys it.

Why Use Automatic Builds?

• Faster Deployment – Keeps your application up to date with every Git push.
• Less Manual Work – Automates the build and deployment process.
• Flexible Workflows – Supports multiple deployment strategies, including registry-based workflows.

Enabling Automatic Build ensures seamless and reliable updates, while turning it off provides more control over deployments. Choose the approach that best fits your workflow!