appbuilder-cicd-pipeline

Automate App Builder CI/CD setup with GitHub Actions workflows.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill appbuilder-cicd-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appbuilder-cicd-pipeline
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/appbuilder-cicd-pipeline
Command: npx skills add https://github.com/valithedge/etisalatedge --skill appbuilder-cicd-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Automates end-to-end CI/CD setup for App Builder projects, turning manual deployment tasks into repeatable workflows.

Core Features & Use Cases

  • Generates GitHub Actions workflows (Stage, Production) using aio CLI actions and patterns for Azure DevOps and GitLab CI.
  • Handles OAuth S2S secrets injection, multi-workspace promotion (stage → prod), and manifest validation gating.
  • Use cases include automating build, test, and deploy of App Builder apps across environments, and extending to non-GitHub CI systems via references.

Quick Start

Bootstrap starter workflows with aio app add ci and tailor them for Stage and Production deployments.

Frequently Asked Questions about appbuilder-cicd-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate App Builder deployments using GitHub Actions?

Automating App Builder deployments involves generating GitHub Actions workflows for Stage and Production environments. This process uses aio CLI actions to handle builds, tests, and deployments, turning manual tasks into repeatable CI/CD pipelines.

What is needed to set up multi-workspace promotion for App Builder?

Setting up multi-workspace promotion requires OAuth S2S credentials, the aio CLI, and a configured workspace.json file. You must configure 14 specific secrets per workspace to successfully promote applications from stage to production environments.

Can I use these App Builder CI/CD patterns with Azure DevOps or GitLab CI?

Yes, the generated GitHub Actions workflows provide deployment patterns applicable to Azure DevOps and GitLab CI. The Skill includes references that help you translate the core aio CLI deployment steps into non-GitHub CI systems.

How do I manage OAuth S2S secrets injection in App Builder workflows?

Managing OAuth S2S secrets injection requires defining 14 secrets per workspace within your CI/CD environment. The generated workflows automatically pull these secrets during deployment to authenticate the aio CLI across Stage and Production.

How do I bootstrap starter workflows for an App Builder project?

Bootstrapping starter workflows is done by running the `aio app add ci` command. This command generates initial GitHub Actions templates that you then tailor specifically for your Stage and Production deployment requirements.

Does App Builder CI/CD support manifest validation gating?

Yes, manifest validation gating is supported within the generated GitHub Actions workflows. This feature ensures your App Builder application manifest is validated successfully before proceeding with the deployment to the target workspace environment.