CI/CD Home
Why choose sfdx-hardis?
There are many ways to do DevOps with Salesforce. Each has its advantages and limitations, as shown in the following comparison table.
Because it is user-friendly
Every persona can be autonomous in their tasks: Admins, Developers, Release Managers and even Project Leaders.
| Role | How they use sfdx-hardis |
|---|---|
| Admins | Build their pull requests using the VS Code extension with clicks. No command line required. |
| Developers | Same as Admins, + understand what's happening under the hood with the Salesforce CLI, thanks to the Advanced mode in the UI. |
| Release Managers | Configure the CI/CD process using the Visual DevOps Pipeline Builder Follow the Pull Requests and Deployments thanks to the DevOps Pipeline View |
| Project Managers | Follow application lifecycle management using sfdx-hardis native integrations with ticketing systems like Jira and Azure Boards. |
Because it is powerful
Advanced features make sfdx-hardis a credible alternative to expensive Salesforce DevOps tools.
| Feature | Description |
|---|---|
| Delta Deployments | Improve performance by deploying only updated metadata. |
| Overwrite Management | Define which metadata will never be overwritten if it already exists in the target org. |
| Smart Apex Test Runs | Skip tests when a pull request to a sandbox cannot break Apex tests to improve performance. |
| Automated source cleaning | Clean profiles of attributes that exist in permission sets, tidy flow element positions, and more. |
| Integration with messaging platforms | Receive detailed deployment notifications on Slack, Microsoft Teams, and email. |
| Integration with ticketing systems | Integrate with Jira, Azure Boards, or any other tool. |
| AI integration | Help resolve deployment issues (Agentforce or direct calls to OpenAI, Anthropic, Gemini). |
We provide ready-to-use CI/CD pipeline workflows for the following Git platforms, with the results of deployment simulation jobs posted as comments on pull requests:
| Platform | CI/CD template |
|---|---|
| GitLab | GitLab CI configuration |
| Azure DevOps | Azure Pipelines checks, Azure Pipelines deployment |
| GitHub & Gitea | GitHub Actions / Gitea workflow checks, GitHub Actions / Gitea workflow deployment |
| Bitbucket | Bitbucket Pipelines |
| Jenkins | Jenkinsfile |
Pipelines can easily be adapted to other platforms like TeamCity.
Here is an advanced example of a Salesforce CI/CD pipeline that you can define using sfdx-hardis. You can define much simpler branch/org models to manage only RUN operations.
See advanced Q&A in the following article.
Because there are no license costs
As everything is open source, there are no license costs!
In comparison, many Salesforce DevOps vendors charge more than 250€/user/month per contributor.
You can handle everything yourself, or ask Cloudity Professional Services for support.
Because it is widely adopted
sfdx-hardis CI/CD is used in production by major companies around the world.
It is also featured in many conferences, blogs, and webinars.
See the presentation of sfdx-hardis at Dreamforce!
See slides of the Dreamforce '23 session
See a detailed article on SalesforceDevOps.net
Get started
Setup sfdx-hardis
If you are comfortable with Git, Salesforce CLI, and DevOps, you can set up and use sfdx-hardis CI/CD on your own.
You can also contact us at Cloudity. Our Professional Services team will be glad to assist you with:
- Technical setup and initialization from your existing Salesforce production org
- Release management strategy definition
- Training for your contributors and release managers
- Change management to accelerate DevOps adoption in your organization
Please read the Setup Guide to learn how to initialize and maintain a Salesforce CI/CD project.
As a Contributor
Please read the Contributor Guide to learn how to work on CI/CD projects as a Business Analyst, Salesforce Administrator, or Salesforce Developer.
As a Release Manager
Please read the Release Manager Guide to learn how to be a release manager on a Salesforce CI/CD project.