Salesforce DevOps in your favorite CI/CD platform, using reliable and widely adopted tools and practices.
Rather than reinventing common CI/CD functionality to be a one-stop shop, OrgFlow instead focuses on bringing Salesforce DevOps to existing CI/CD platforms, so you can leverage their already excellent and mature features for things like user management, Git version control, work item tracking, pull requests, schedules and triggers, and reporting and analysis.
Because OrgFlow is a cross-platform CLI that runs natively on macOS, Windows, Linux and Docker, as long as your CI/CD platform lets you run scripts, then you can almost certainly run OrgFlow on it. We also provide native extensions for a growing number of the most popular platforms such as GitHub Actions and Azure DevOps, making the integration experience even easier.
A robust scheduling engine is a core feature of most CI/CD platforms. By running OrgFlow in your CI/CD platform, you can automate Saleforce DevOps activities on a recurring schedule using cron expressions, or initiate activities based on events in the platform such as a pull request being updated.
Run Apex tests on a schedule and automatically notify your team on failed tests to catch bugs early. Avoid blocked deployments by knowing in advance when tests will fail. Improve the robustness of your sandboxes by ensuring that changes that cause tests to fail do not propagate to other environments.
Use popular third-party tools to regularly perform static code analysis, linting and validation, to help maintain a high quality Salesforce code base. Monitor your code quality metrics over time using popular analysis and reporting tools, or send notifications to your team when new issues are discovered.
Schedule jobs to frequently commit metadata changes to Git, in order to build up a rich change history in your repository. Reduce risk by using your Git-based change history to easily revert problematic changes. View line-level changes to metadata over time, and trace those changes to the individual Salesforce users who made them.
Set up a CI pipeline to trigger a deployment to the appropriate Salesforce org whenever changes are pushed to a particular Git branch. Watch for changes to specific files in your repository and generate alerts or trigger workflows as required.
Create a scheduled workflow out of hours to automatically flow any metadata changes from production upstream to your development environments, to ensure admins and developers are working on an up-to-date baseline and help avoid time-consuming merge conflicts down the line.
Most CI/CD platforms provide pull request functionality as in integral part, and OrgFlow was designed to fit nicely into pull request workflows. Incorporating pull requests into your Salesforce DevOps pipeline can help you reduce deployment risks and increase transparency and confidence in your process.
A pull request gives admins and developers a visual preview of what's about to be flowed from one environment to another — line by line at the metadata level. Proposed changes can be viewed before they are merged and deployed, giving admins and developers an opportunity to ensure the expected changes — and only the expected changes — are there.
Pull requests allow admins and developers to conduct peer review of proposed changes, vote for approval or rejection, and have threaded discussions inline, right next to the changed metadata or code lines themselves. This helps maintain a high quality code base and build a team culture of shared responsibility.
By running an OrgFlow validation-only merge flow automatically on any new or updated pull requests, you can validate how the proposed changes will deploy into the target environment — including test execution — and catch and fix any deployment problems before any changes are actually merged and deployed.
Most CI/CD platforms let you set up policies to run workflows and checks in response to new and updated pull requests. You can use OrgFlow to run Apex tests, and other popular tools to perform static code analysis, linting and validation — and then visualize and fix any discovered issues before any changes are merged and deployed.
OrgFlow export Apex test results to formats that CI/CD platforms can understand, which means you can advantage of advanced reporting and analysis features to know exactly when a test started failing, and pinpoint the exact change that caused it. Many CI/CD platforms even let you create work items and link them to the failing tests, to plan and track the required fixes.
Many CI/CD platforms provide robust work tracking capabilities with boards, backlogs and process management. By running your Salesforce DevOps on the same platform, you can associate Salesforce metadata changes in Git with work items to increase accountability, make progress more visible, and trace individual line-level changes all the way to the work items that initiated them.
Your CI/CD platform can also be a great hub for team members to interact with your Salesforce DevOps pipeline. Many platforms sport deep integration with collaboration platforms like Slack or Microsoft Teams. Send alerts to your team on important events, such as automated Apex tests failing, or even let users initiate DevOps workflows by writing messages in Slack — your engineering creativity is the only limit.
Building and running your Salesforce DevOps in a CI/CD platfrom puts a whole universe of popular tools and services at your fingertips. You get instant access not only to anything on your CI/CD platform's extension marketplace, but also anything you can find in places like NPM, Homebrew, Winget, Linux package repositories or — if you're using self-hosted agents — anything you can install manually, too.
Don't take our word for it — see for yourself! Try OrgFlow free for 2 months. No limits. No strings attached. No credit card or billing information required.Try Now