website logo
Sign Up PricingApp Templates
⌘K
⏰Changelog
📚Ready-to-use Templates
Strapi Serverless
Medusa Server
Appwrite
SPA on CloudFront
Amazon EKS
Node.js
n8n Workflow Automation
Next.js
🚀Getting started
Create an account in Microtica
Create an application from template
Import an existing application
Scaling Applications in Microtica
Assign a Custom Domain
🔄Integrated CI/CD
Manual deployments
Automated deployments
Deploy from multiple Git branches
Pipeline Notifications
Deployment Insights
đŸšĻPipelines
Pipeline Syntax
Steps
Stages
Artifacts
Variables
â†Šī¸Automated Rollbacks
💰Cloud Cost Optimization
Cost Reports
Cost Dashboard
Automated Saving Schedules
🔗Integrations
Connect an AWS account
Connect an Existing Kubernetes Cluster
Connect a Container Registry
🤖Migrate to Microtica
Migrate from Heroku to AWS
âš™ī¸Project Settings
Manage teammates
Manage pricing plan and billing
Docs powered by
Archbee
Integrated CI/CD

Deploy from multiple Git branches

7min

Microtica allows you to configure and automate deployments from multiple Git branches to different cloud environments. This capability empowers you to manage separate deployment pipelines for various branches, enabling parallel development and testing workflows. Microtica's intuitive user interface (UI) allows you to easily configure the desired cloud environments and specify the branches from which to trigger automated deployments.

īģŋ

deploy to multiple Git branches
īģŋ

When you signup to Microtica a development environment is created by default. But to have a reliable software development lifecycle, you should implement separate environments for development, testing, and production. This way you can maintain a controlled and efficient development process, minimize risks, validate changes thoroughly, and deliver reliable software to your users.

In Microtica, you can create another environment using the ready-made templates.

This guide provides step-by-step instructions for creating a testing environment using the Import template and deploying from a testing branch.

Prerequisites

Before proceeding, ensure you have the following prerequisites:

  • A Microtica account with the necessary permissions to create environments.
  • A repository containing your app code.
  • A testing branch (e.g., "test") within your Git repository.

Step-by-Step Guide

Follow these steps to create a new testing environment using the Import app template and deploy from your testing branch:

  1. īģŋLog in to your Microtica account and navigate to the Microtica portal.
  2. (Optional) Access the Environments section in the project and click on the Create Environment button.
  3. Click the Deploy app button in the header.
  4. Select the Import existing app template from the available template options.
  5. In the first section, choose the Git repository where your code is located.
  6. Under the Branch input, specify the testing branch you want to use (e.g., "test").
  7. Click the Next button to import the repository and branch.
  8. Configure any necessary environment variables according to your testing requirements.
  9. Click the Next button to save the environment configuration.
  10. In the Choose where to deploy section, click the Create Amazon EKS Cluster button and a popup will show up where you need to select the environment where you want to create the EKS cluster and deploy the app. If you created an environment in step 2, go ahead and select that environment. If not, you can create a new environment now.
  11. Enter the required information for your new testing environment, such as the name and description, click on Create.
create amazon kubernetes cluster
īģŋ

12. Add your AWS account credentials for the environment, and then specify the cluster name and click on Continue.

13. Review your selection and start your deployment. With this, you have successfully created a new testing environment in Microtica, that will deploy from your testing Git branch.

deployment summary
īģŋ

Microtica will automatically deploy the code from your testing branch to the newly created environment on every git-push.

This setup allows you to test and validate your application within a dedicated environment while maintaining a separate branch for testing purposes.

Video Guide for Automated Deployments from Multiple Git Branches

Take a look at this video of a scenario deploying automatically from the master branch and another feature branch.

<div style="position: relative; padding-bottom: 62.5%; height: 0;"><iframe src="https://www.loom.com/embed/f59cf78251f74984947ea78f8ce79023?sid=ebe02c40-abbf-43b6-94a9-9fc88c270ea0" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
īģŋ

Microtica's automated deployments from multiple Git branches enable parallel development and testing workflows, ensuring efficient and reliable deployments to different cloud environments. By following the step-by-step guide above, you can configure multiple CI/CD pipelines in Microtica, associate them with specific Git branches, and automate your software delivery process for each branch independently.

Updated 10 Jul 2023
Did this page help you?
PREVIOUS
Automated deployments
NEXT
Pipeline Notifications
Docs powered by
Archbee
TABLE OF CONTENTS
Prerequisites
Step-by-Step Guide
Video Guide for Automated Deployments from Multiple Git Branches
Docs powered by
Archbee