It was great having Rob presenting (virtually) to our Prague User Group what the DevOps is about and whether we should care or worry about it. As we are hearing more and more about it sounds like a great idea to learn more as well. Especially as Salesforce invented the DevOps Center (though we should admit it didn’t get much love in recent years, but that should change as we’ve been promised at Dreamforce).
- it isn’t just for teams, even if you are solo admins you can benefit from not getting yourself in a mess;
- additional technical tool isn’t usually enough, the culture/communication need to change;
- getting changes in the version control should be the most important step as you will have the log of changes, when, ideally why, who, etc.;
- peer review, PMD, Clayton and other things to improve code (and hence delivery) quality and through that minimize the technical debt as well;
- backup – yes, that might be part of the thing as well;
- speeding up the deployment might be also important as it will free your time to do better things, such as speaking with customer what else you can help them with;
- didn’t know before what „git“ stands for – „an unpleasant or contemptible person“;
- great explanation of changes vs staged changes (in VS Code) – just now I realized it really mimic change sets and the things in the change set are the „staged“ changes (obviously only after you commit them);
- why they always have it so quick and it took so much time on my machine? Things like downloading metadata, etc are done in a blink of eye on everyones demo and takes a few minutes on all my projects 🙁
- worry later about branching, merging, etc – sounds like trunk based development for those in a know?
- while version control allows you to roll back code, as an admin who starts using it, you probably shouldn’t aim for that. Take the version control as a place which shows you what has been, changed what and why but rather redo the changes manually then trying to somehow roll back. Using additional tools might simplify that though;
- Trailhead has some things to learn, the DevOps Launchpad might be more relevant (yes, run by Gearset). There is also great book by Rob Salesforce DevOps for Architects: Discover tools and techniques to optimize the delivery of your Salesforce projects and the DevOps Dreamin‘ conference regularly switching between Chicago and London;
- continues delivery will also have an impact about communication of changes inside your company – the „standard“ release notes sent via email or shared on intranet probably aren’t the right way forward with multiple deployments per day.
DevOps is not a tool only, it is also about culture, approach, not worrying about deploying again.
Presentation and recording available.