CI/CD templates for Power Platform Application Lifecycle Management (ALM).

Part of the Power Platform Developer Suite ecosystem.

name: Deploy to QA

on:
  push:
    branches: [develop]

jobs:
  deploy:
    uses: joshsmithxrm/ppds-alm/.github/workflows/solution-deploy.yml@v1
    with:
      solution-name: MySolution
      solution-folder: solutions/MySolution/src
      build-plugins: true
      package-type: Managed
    secrets:
      environment-url: ${{ vars.POWERPLATFORM_ENVIRONMENT_URL }}
      tenant-id: ${{ vars.POWERPLATFORM_TENANT_ID }}
      client-id: ${{ vars.POWERPLATFORM_CLIENT_ID }}
      client-secret: ${{ secrets.POWERPLATFORM_CLIENT_SECRET }}

Granular, reusable actions for building custom workflows:

See Actions Reference for detailed documentation.

The import action automatically:

• Compares versions - Skips import if target has same or newer version
• Retries transient failures - Handles concurrent import conflicts with configurable retry
• Applies deployment settings - Auto-detects environment-specific configuration files

- uses: joshsmithxrm/ppds-alm/.github/actions/import-solution@v1
  with:
    solution-path: ./exports/MySolution_managed.zip
    solution-name: MySolution
    skip-if-same-version: 'true'
    max-retries: '3'
    settings-file: ./config/qa.deploymentsettings.json

Solution exports often contain volatile changes that aren't real customizations:

• Solution.xml version timestamps
• Canvas app random URI suffixes
• Workflow session IDs
• Whitespace-only changes

The analyze-changes action filters these, preventing unnecessary commits.

Validate solution quality before deployment:

- uses: joshsmithxrm/ppds-alm/.github/actions/check-solution@v1
  with:
    solution-path: ./exports/MySolution_managed.zip
    fail-on-level: High  # Critical, High, Medium, Low, Informational
    geography: unitedstates

• GitHub Actions Quickstart
• Authentication Setup

• Workflows Reference - All reusable workflows documented
• Actions Reference - All composite actions documented
• Consumption Guide - When to use actions vs workflows
• Features Guide - Deep dive into advanced features
• Troubleshooting

• Azure Integration - Bicep modules and naming
• Azure OIDC Setup - GitHub Actions authentication
• Azure Coordination - Coordinating Azure and Dataverse deployments

• ALM Overview - Philosophy and approach
• Branching Strategy - Recommended git workflow
• Environment Strategy - Dev/QA/Prod patterns

ppds-alm/
├── .github/
│   ├── actions/                    # Composite actions
│   │   ├── setup-pac-cli/
│   │   ├── pac-auth/
│   │   ├── export-solution/
│   │   ├── import-solution/
│   │   ├── pack-solution/
│   │   ├── build-solution/
│   │   ├── check-solution/
│   │   ├── analyze-changes/
│   │   ├── copy-plugin-assemblies/
│   │   └── copy-plugin-packages/
│   └── workflows/                  # All workflows
│       ├── _ci.yml                 # CI for this repo (internal)
│       ├── solution-export.yml     # Reusable workflows (workflow_call)
│       ├── solution-import.yml
│       ├── solution-build.yml
│       ├── solution-validate.yml
│       ├── solution-deploy.yml
│       ├── plugin-deploy.yml
│       ├── plugin-extract.yml
│       ├── solution-promote.yml
│       └── azure-deploy.yml
├── bicep/                          # Azure Bicep modules
├── docs/
├── CHANGELOG.md
└── README.md

Use version tags for stability:

Contributions are welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Run actionlint on GitHub Actions workflows
5. Test with actual CI/CD environment
6. Submit a pull request

MIT License - see LICENSE for details.

• Report Issues
• Documentation