sf project deploy start: flags, dry run, test levels and errors
What sf project deploy start does, the flags that matter, dry run vs validate, the test levels, what report, preview and resume do, and what each error means.
Read Article
Salesforce engineering notes
Salesforce engineering, written up from the work
I write up the Apex, Lightning Web Components, integration and Salesforce CLI problems I meet on client projects, with the sources, for the next person who hits them.
Latest Engineering Brief
Keep Reading
View All
Recent Deep Dives
sf project deploy validate vs start: which to run and when
Validate then quick for production, start for sandboxes: which sf project deploy command fits each environment and test level, what fails, and how to recover.
Salesforce CLI JWT auth in GitHub Actions: no browser login
Set up headless Salesforce CLI authentication in GitHub Actions using JWT so CI can deploy without browser login prompts.
Salesforce CLI DevOps Playbook: Auth, Deploy, CI/CD Fixes That Actually Work
Salesforce CLI reliability playbook: JWT auth for CI, validate then quick deploy, test levels by org, sandbox deploys without tests, pending deployments.
How to Fix Salesforce CLI NPM Installation Errors
Fix Salesforce CLI npm install errors: EACCES, sf command not found, PowerShell execution policy, sfdx-cli conflicts and network errors.
How to Install Salesforce CLI with NPM
Install Salesforce CLI with npm, migrate from sfdx-cli to @salesforce/cli, and follow best practices for version management and CI/CD pipelines.
Contract work
Working through something like this on your own org?
I take on contract work: scoped Apex, Lightning Web Components, integration and deployment-pipeline deliverables, written by me and shipped with tests and documentation. If one of the articles above is close to your problem, the services page says how an engagement runs.