Using docker images in your CI/CD

Put simply, the sfpowerscripts Docker image will allow you to run your builds / releases within a container, which is like a virtualized environment running on a physical system and has its own OS, apps etc. For more information on Docker and containerization, visit Docker's documentation.

The sfpowerscripts Docker image is available at:

We recommend using the sfpowerscripts Docker image because it will grant your CICD pipelines greater reliability - avoiding breakages due to updates in sfpowerscripts or its dependencies (e.g. SFDX CLI, SFDMU). Each sfpowerscripts image has static versions of sfpowerscripts and its dependencies, which means that it will not be affected by any updates.

Utilizing the sfpowerscripts Docker image will give you the surety that your builds are consistently running in the same environment - meaning that you can safely assume that discrepancies between builds are not a result of environment setup.

Most of all, the sfpowerscripts Docker image makes things easy. We have already done all the hard work of creating an image that has all the required dependencies installed (Node, JDK, sfpowerkit, sfdmu, etc.). All that is required from you is to pull the image from the registry and run it.

To use this docker in your CI/CD Pipelines, please check the documentation of your CI/CD provider.

Checkout below samples

Azure Pipelines
GitHub Actions
Azure Pipelines
vmImage: 'ubuntu-latest'
# Specify a container job to use the docker image. Read more about using
# container jobs at
container: dxatscale/sfpowerscripts:latest
GitHub Actions
name: sfpowerscripts prepare
# Definition when the workflow should run
- cron: '0 0 * * *'
# Read more about using contaniers
# Jobs to be executed
runs-on: ubuntu-latest
container: dxatscale/sfpowerscripts
Edit on GitHub