Setup Salesforce Deployment Assistant

Configure integrations

Make sure to have configured your GitHub, Gitlab, Azure Pipelines or BitBucket integration so the deployment assistant can post its help in Pull Request comments.

If you want to supercharge Salesforce deployment assistant with AI, process sfdx-hardis AI setup.

You can also receive Slack, Ms Teams and Email notifications in case of successful deployment.

If you configure JIRA or Generic Ticketing integrations, ticket numbers will be extracted and displayed in the Pull Request comment.

Using sfdx-hardis CI/CD

If you are using sfdx-hardis CI/CD, you are already all set !

Using custom CI/CD pipeline

Replace your calls to Salesforce CLI by calls to sfdx-hardis commands wrapper.

sfdx command	Corresponding sfdx-hardis wrapper command
sf project deploy start	sf hardis:project:deploy:start
sf project deploy validate	sf hardis:project:deploy:validate
sf project deploy quick	sf hardis:project:deploy:quick
sfdx force:source:deploy (removed on 6 november)	sf hardis:source:deploy
sfdx force:source:push (removed on 6 november)	sf hardis:source:push
sfdx force:mdapi:deploy (removed on 6 november)	sf hardis:mdapi:deploy

Configure your GitHub, Gitlab, Azure Pipelines or BitBucket integration so the deployment assistant can post its help in Pull Request comments.

Notes:

sfdx-hardis deployment assistant now works better with --json option please use it :)

Example

Replace:

sf project:deploy:start -x manifest/package.xml --checkonly

with:

sf hardis:project:deploy:start -x manifest/package.xml --checkonly

Advanced example

Replace:

sf project deploy start --dry-run --source-dir force-app --ignore-warnings --ignore-conflicts --test-level RunLocalTests --coverage-formatters json-summary --verbose --wait 120 --json

with:

sf hardis project deploy start --dry-run --source-dir force-app --ignore-warnings --ignore-conflicts --test-level RunLocalTests --coverage-formatters json-summary --verbose --wait 120 --json