Salesforce Wellington User Group - devops for admins by David Smith
- 2. 2 Devops for Admins (and other people too)
- 3. 3 David Smith Lead Architect - GravityLab.nz CTO - FiveToFlow.com linkedin.com/in/davidsmithnz
- 4. 4 What are the issues here? ● Building changesets are hard! ● No source control ● Deploying with changesets is painful ● Lack of auditability ● Not a lot of coordination
- 5. 5 What is DevOps in a Salesforce context? The ultimate goal of Salesforce DevOps is to improve the speed, quality, and reliability of software delivery and operation, while reducing risk and increasing efficiency. ● Getting changes deployed effectively ● Keeping your system working by managing risk ● Managing testing effectively
- 6. 6 Change Sets Point to Point Deployments Deploy from Source Control CI/CD Fully Integrated Pipeline Different levels of DevOps
- 7. 7 Where do I start? 1. Stop using change sets. There is a better way. Use tools that do a better job. 2. Think about source control next - track your changes 3. How do you work with multiple developers/functionals? 4. Get faster and more betterer.
- 9. 9 What tools are available?
- 10. 10 • Free plan - try it out! • Can act as a simple point to point, easily upgradeable to source control, from there you can plug in CI/CD • Diff etc are super easy to understand.
- 11. 11
- 12. 12 When would I use Copado? • Just starting your devops journey. Source control seems complicated, and you just want a better tool. • You want to start using source control, but you want to manage each step of the process closely.
- 13. 13 • Free • Source control baked in from the start. • Follows release management processes • Expandable by ISV’s • Build around deployment strategy
- 14. 14 3 core principles: • Pipelines • Work items and bundles • Source control
- 15. 15 When would I use Salesforce Devops centre? • You’ve got a well defined release strategy and process. • You’re working with project managers and other roles like that, who want to bundle work into work items and control them through release processes. • You’re happy using github, and leveraging github internal processes to put rules around your releases.
- 16. 16 The Scenario
- 17. 17 Demo
- 18. 18 Questions?
- 19. 19 ● Arrive, pick up badge, Tuesday morning ● Keynotes ● Floor layout ○ 3 levels ● Things to do What happens at TDX?
- 20. 20 ● 5 free api user accounts ● Slack will replace chatter one day. Not soon. ● User management will get better - see permission management stuff. No real work going into setup, but working on general lightning performance ● There is an internal UI refresh happening…dark mode coming as part of that. ● AI everywhere - Content will benefit most imo. ● 70% of slack customers also use teams. Biggest Takeaways
- 21. 21 ● Game changer. In next release ● REACTIVE SOQL - INTO REACTIVE DATATABLE! Reactive flow
- 22. 22 Thanks!