Automatic Builds on Git Pushes

CloudStation supports automatic builds triggered by Git pushes, enabling seamless integration and continuous deployment for your projects. This feature ensures that your applications are always up-to-date with the latest changes in your codebase.

What It Does

When you enable the "Automatic Build" feature by toggling the corresponding button in your project settings, the following actions are automatically performed upon every Git push:

  1. Detect Changes: CloudStation detects the push event and identifies the changes in your repository.

  2. Trigger Build: A new build process is initiated using the specified "Build Context". By default, the "Build Context" is set to /. If a Dockerfile is not found in this directory, CloudStation will default to using the Nixpacks builder. For more details on configuring builders, refer to the Builders Documentation.

  3. Build Execution: CloudStation executes the build process based on the detected builder configuration.

  4. Deployment: Depending on your deployment settings, one of the following actions will be performed once the build is completed:

    • Build and Deploy: The application is automatically deployed with the new build.

    • Build and Push to Registry: The build is pushed to a specified container registry.

    • Build, Push, and Deploy: The build is pushed to a specified container registry and then deployed. For more details on configuring private registries, refer to the Private Registry Documentation.

What Happens When "Automatic Build" is Off

If the "Automatic Build" feature is turned off, users will need to manually trigger the build process from CloudStation UI. This can be beneficial in scenarios where:

  • Controlled Deployments: You want to review and test changes before deploying them to production.

  • Selective Builds: You may want to build and deploy specific changes rather than every push, giving you greater control over the deployment process.

  • Scheduled Releases: You prefer to deploy at specific times rather than immediately after each commit, allowing for planned and coordinated releases.

Manual Build Process

  1. Access Project: Navigate to your project in CloudStation dashboard.

  2. Trigger Build: Go to setting and Use the "deploy changes" button in the UI to manually start the build process.

Deployment Settings

  • Build and Deploy: Automatically deploys the new version of your application after a successful build.

  • Build and Push to Registry: Pushes the new build to a configured container registry.

  • Build, Push, and Deploy: Pushes the new build to a configured container registry and deploys it.

Benefits

  • Continuous Deployment: Ensures your application is always up-to-date with the latest changes from your Git repository.

  • Automation: Reduces manual intervention by automating the build and deployment processes.

  • Flexibility: Supports various deployment settings to match your workflow, including building and pushing to registries.

By enabling the "Automatic Build" feature, you streamline your development workflow, ensuring that every code change is quickly and reliably built and deployed. Conversely, turning it off allows for more controlled and deliberate deployment strategies.