CI/CD for App Builder Applications: Overview

Continuous integration and continuous delivery (CI/CD) is a crucial component for the success of any development team, including teams developing App Builder apps. By automating deployment, CI/CD allows the development team to build and deploy apps free of any variances that may arise from building and deploying the app from a developer's machine.

Before you dive into CI/CD we recommend you read our deployment guide to familiarize yourself with general concepts about App Builder app deployment.

Setting up CI/CD pipeline using GitHub Actions

To deploy App Builder apps, App Builder supports a CI/CD pipeline using GitHub Actions. Please read step-by-step instructions to set up your CI/CD pipeline here: Setting up a CI/CD pipeline using GitHub Actions.

The following GitHub workflows are provided out of the box:

CI/CD with Github Actions

GitHub actions for AIO CLI

These GitHub Actions have been built to support the use of the CLI in a CI/CD workflow running within GitHub infrastructure. They are used in the default App Builder Apps workflows, and can also be used in custom GitHub workflows you build:

Both actions have been published and can be found on GitHub Marketplace. See CLI Setup and Apps.

Setting up a custom CI/CD pipeline

If you cannot use GitHub actions for your CI/CD pipeline for any reason, you can also build a custom CI/CD pipeline using any industry-leading CI/CD tool and the AIO CLI. Read our guide on Setting up a custom CI/CD pipeline to deploy App Builder apps.

Next steps

Set up CI/CD using GitHub Actions.

Set up custom CI/CD pipeline.

Continue to Credential Rotation.

Return to Deployment Overview.

Return to the Guides Index.