Masterclass · October 2026
From change sets to a Salesforce pipeline you own
Several partners, one org and three Salesforce releases a year: without a binding release process every change becomes a risk. I show step by step how to get from change sets to a pipeline you own, with open source such as sfdx-hardis or with commercial platforms.
- 10chapters
- 17articles
- DE · ENGerman and English
Deadlines
Deadlines that affect your pipeline
These changes hit your pipeline and your integration users. Notice them too late and you find out from a failed deployment.
- Local Salesforce DX MCP Server reaches end of life →
- SOAP login() needs the Use Any API Auth permission →
- OAuth username-password flow for connected apps ends →
- SOAP login() in API versions 31.0 to 64.0 is removed
- SOAP, REST and Bulk API versions 31.0 to 40.0 are retired
Chapters
Ten chapters, from change sets to stable operations
From the first change set to controlled operations, in the order you should tackle it in your project.
- Chapter 01:
Why releases decide
The core terms, the cost of bad releases with several partners and five maturity stages from change sets to your own pipeline. - Chapter 02:
Ownership and roles
Who owns repository and pipeline, which four roles a release needs, who approves what and how the process survives a partner change. - Chapter 03:
Environments and branches
How sandboxes, scratch orgs and branches fit together so developer orgs stay current and hotfixes do not get lost. - Chapter 04:
Tools compared
From change sets to commercial platforms: which DevOps tool fits your Git platform, your team and your implementation partners. - Chapter 05:
Building the pipeline
The building blocks of a Salesforce pipeline, from pull requests, test levels and delta deployments to a login without passwords. - Chapter 06:
Quality, tests, reviews
Which reviews, tests and automated checks every change must pass before it is merged, for code and for flows. - Chapter 07:
Data and configuration
Which configuration and reference data is not metadata, how it moves through the pipeline and how sandboxes stay masked. - Chapter 08:
Release planning
How to align your release calendar with the three Salesforce releases, release updates and retirements. - Chapter 09:
Operations and monitoring
What go-live adds to the job: daily org monitoring, tested backups, visible technical debt, DORA metrics and a hotfix path. - Chapter 10:
Rollout and roadmap
Seven phases from change sets to a client-owned pipeline, with training, metrics and an outlook on coding agents.
Articles
Articles in the masterclass, one question each
Each article answers one concrete question about releases and operations. Sorted by topic, so you can look things up directly.
Foundations and ownership 4 articles
Why the release process decides enterprise programmes and why the client should own it.
Tools 4 articles
sfdx-hardis, DevOps Center and commercial platforms: what each covers and when it fits.
Releases and platform changes 4 articles
What Salesforce releases and retirements change in your pipeline and when to act.
AI in the pipeline 5 articles
Reviews, quality gates and data rules when coding agents contribute to the release.
Contact
Want to put your release process on solid ground?
A short conversation shows where your process stands today and which step matters next.
Book a call (opens Microsoft Bookings in a new tab)Pick a slot in my calendar via Microsoft Bookings. Prefer to write? Use the form and I’ll get back to you.
Rather talk right away? +49 221 98656758