Thoughts on technology and innovation
Ted Husted - Release Engineer
With Winter '17 in the rear-view mirror, we're already well on our way to Spring '17 -- which will be our 15th major release of Nimble AMS. Fifteen seems like a milestone to me.
DevOps on a cloud platform, like Salesforce, brings its own set of challenges, and its own set of safeguards. To keep life simple for our customers, we follow the Salesforce release cadence and change management protocols.
We deliver major versions three times a year, and apply patch versions as needed in between. Before a major release, we update customer sandboxes with a preview version, we run all the local Apex tests for everyone (thanks GearSet!) along with our own set of regression tests, to be sure we stay in the green zone. Production upgrades are rolled out in groups over a two-week period.
Here are a few of the safeguards that are built into the platform to ensure a reliable release process:
Internally, we use several DevOps techniques to be sure we are always release ready and release safe.
For more about how the platform works, see Understanding the Salesforce Architecture: How We Do the Magic We Do (YouTube).
Over the next year or so, the Salesforce DX changes are going to make my life easier, fun even, and I take much comfort in knowing that the platform is watching my back.
Do you miss the old days, when big-bang releases came out every three years? Or do you prefer today's release-often approach?
Ted Husted is a Kaizen Squad developer on the Nimble AMS product crew. "We make the good changes that create a great product." For more, follow @tedhusted on Twitter.