Ad
More Related Content
What's hot (20)
Similar to Discover salesforce, dev ops and Copado CI/CD automations (20)
Ad
More from JackGuo20 (6)
Ad
Recently uploaded (20)
Discover salesforce, dev ops and Copado CI/CD automations
- 1. Discover Salesforce DevOps with Copado CI/CD automations
- 2. Donโt wait until the end to ask your question! โ Technical support will answer questions starting now. Respect Q&A etiquette โ No need to repeat questions. The support team is working their way down the queue. Head to the Trailblazer Community โ More questions? Visit http://trailblazer.salesforce.com/answers Have Questions?
- 3. Go Social @salesforcedevs Salesforce Developers Salesforce Developers Salesforce Developers
- 4. Forward-Looking Statement by Salesforce This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include โ but are not limited to โ risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Website. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Statement under the Private Securities Litigation Reform Act of 1995
- 5. Your Hosts โข Fifteen years IT and Management experience โข 16 Salesforce Certifications โข Four years full-time focus on Salesforce DevOps โข Senior Product Manager at Copado โข 15 Years on the Salesforce Platform โข 7 Yrs at Salesforce on the Platform Team โข Focus: Cloud App Dev, APIs, Integration โข SVP Marketing and Alliances Copado Andrew Leigh Andrew Davis
- 6. Agenda 01 Why DevOps for Salesforce? 02 Delivery Performance 03 Delivering Innovation 04 The Innovation Pipeline 05 Quality and Testing 06 Release and Deploy 07 Questions? Agenda
- 8. DevOps Enables You to Operate Salesforce at Scale Only 10% of CIOs say they are very successful at rapid software development and deployment INNOVATION VELOCITY TRUST & QUALITY CREATE TEST RELEASE PLAN MONITOR Go-Live Gap DELIVERY PIPELINE SFDC DevOps Needs FEEDBACK LOOP SALESFORCE PLATFORM Go Live! Merge Conflicts No Collaborative Development Tools No structured release process No source repositories Trouble Keeping Sandboxes in sync No Integration with 3rd party DevOps Tools Lack of version control Lack of compliance DEPLOY
- 9. Why Salesforce DevOps? Which of these areas do you believe you could improve for your organization if your team was able to prioritize improvements to your Salesforce development and release process over the next 3-5 years? Salesforce DevOps Is Paying Off $5 Million In Benefits 17% of Respondents What business impacts have you seen from your Salesforce DevOps strategy? Why Do Salesforce Customers Move to DevOps?
- 10. The Challenge: Two Competing Motivations Developers focus on Change Ops/Admins focus on Stability * Salesforce Admins function more like developers!!!
- 11. Text โ Text These Two Motivations are in Tension โช Competitive disruption โช Unserved needs โช Inefficient systems โช Excluding people โช Ignoring opportunities โช Unsustainable future Whatโs at risk if we donโt change? Things have to change โฆ. fast โช Trust โช Security โช Compliance โช Quality โช Users โช Customers โช Money Whatโs at risk if we change? โฆ but thereโs a lot at risk
- 12. DevOps Breaks Down the Silos That Hold Your Team back Change your culture by changing the communication across teams INNOVATION DELIVERY PERFORMANCE โ Faster Time to Market โ More Secure and Stable Releases โ Align Business Goals With Technology โ Optimize Salesforce Performance โ Measure Digital Transformation Progress SECURITYADMIN ARCHITECTDEVELOPER CIO IT SALES MARKETING OPS
- 13. System-level Thinking: Data Driven DevOps
- 14. How Do You Measure Your Performance? โFaster delivery alone merely leads to customer disappointment when the software delivery process defers to velocity without also addressing qualityโ PERFORMANCE FACTORS: โ Size of the Delivery Team โ Number of Users โ Number of Production Orgs โ Amount of Customization โ Use of a DevOps tooling The Four Measures of Delivery Performance Time from code committed to production โข Shorter is better โข Faster feedback cycles โข Adjust to the market How often you release to production โข More is better โข Small batch size โข More market agility How long to recover from failures released to production โข Shorter is better โข Decrease customer exposure โข Decrease down time Percentage of releases requiring rollback or fixes โข Less is better โข Early detection is critical โข Automation is important 8hrs Hourly 10% 60min
- 15. SALESFORCE INNOVATION PERFORMANCE LEAD TIME FROM DEV TO PRODUCTION RELEASE FREQUENCY CHANGE FAIL RATE RESTORE TIME ELITE (Top 13% of SFDC) Less than one hour On Demand 0-15% Less than an hour HIGH (36% of SFDC) Less than one day O Between once per day and once per week 0% - 15% Less than a day MED (43% of SFDC) Between one day and one week Between once per day and once per week 16% - 25% Between one day and one week LOW (8% of SFDC) Between one week and one month Between once per week and once per month 51% - 75% Between one day and one week IMPROVEMENT 2555x Faster 46x More Releases 8x Fewer Failures 96x Faster Restore Time State of Salesforce DevOps 2019 How Do You Compare to Your Peers?
- 16. Real World Example: Benchmark Your Performance Use the 4 Performance Metrics Use Salesforce Native Dashboards Value Stream Mapping Salesforce Analytics Benchmark your Salesforce Innovation Performance
- 18. Salesforce Development There are tons of books, conferences, videos, and groups who can help You donโt need me to tell you how to develop on Salesforce
- 19. Real World Example: Commit Changes via a Command Line Interface Do everything you need from the IDE Leverage Git and SFDC Commands Leverage Agile tools like Jira Leverage User Stories and CCD CLI is a plugin to the SFDC CLI (SFDX) Authenticate & Set User Story Push Changes, Validate, & Submit Use Your Favorite IDE To Develop Solution Commit Changes Repeat as Required TYPICAL DEVELOPER FLOW > sfdx force:auth:web:login Successfully authorized [email protected] with org ID 00D0Y000002HsLKUA0 You may now close the browser > sfdx copado:auth:set -u [email protected] Copado CLI configuredโฆ Step 1: Authenticate > sfdx copado:work:set -a Jira004 User Story US-0031295 configuredใใใใใใ Step 2: Set the User Story using Jira Set the User Story Primary Agile Tool External ID (-a), Copado User Story Name (-u), or Copado User Story ID (-i) Local branch is created and checked out. > git commit -a -m "Updated FinanceManager Unit Test class" Step 3: Make Changes & Commit with Git like always Use any Terminal or Desktop application to deliver changes -a All Changes -m Required message for the commit > sfdx copado:work:pushใใใใใใใใใใใใใ Success: Pushing all commits to User Story US-0031295 โฆ User Story Commits added โฆ Metadata Selections Updated โฆ User Story ready to be submitted. Step 4: Itโs time to push! All changes are pushed to remote branch (Git Host) MD is Linked to User Story Copado Because many developers prefer a CLI
- 20. Salesforce Architecture Technical Debt: The implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach. One of the main roles of architects is to recognize the risk of technical debt and to avert that by proper system design Most of the IT industry struggles with technical debt Time Millionsof LinesofCode
- 21. Salesforce Architecture Our research shows that teams are slowing down as they get larger
- 22. Tight Coupling Examples: โ Emphasis on procedural code (as opposed to functional or object-oriented code) โ Highly complex relationships between code โ No modules or packages
- 23. Loose Coupling Examples: โ Object-oriented design โ Functional Programming โ Modular architecture โ Run-time dependency injection โ Event-driven architecture
- 24. Actual Dependencies in one org Those Dependencies as Packages
- 25. 03 Innovation Delivery RELEASE CONTINUOUS INTEGRATION CONTINUOUS DELIVERY โข Prioritize requirements โข New and updated requests โข Task assignment โข Timeline finalization โข Click and code development โข Commit to version control โข Static code analysis โข CI Pipeline creation VERIFYCREATEPLAN โข Integration tests โข UI Testing โข Requirements testing โข Security testing โข Delivery Pipeline โข Automated Tests โข Metadata Fast Lane โข Monitor work in progress โข Release to users โข Validate features CONTINUOUS INNOVATION MONITOR DEPLOY โข Innovation Performance Metrics โข Dev and Release Dashboards โข Compliance Agile Development Iterative Delivery CI/CD For Salesforce
- 26. Real World Example: The CI/CD Delivery Pipeline "Our highest priority is early and continuous delivery of working softwareโ - The Agile Manifesto, 2001
- 27. โ Changes are made in production that are not propagated to dev and test environments โ Changes are made in dev environments that are never moved to test or prod environments โ Different test environments may have different configurations โ Metadata in different production orgs that is supposed to be consistent may grow increasingly different Environment Management Environments Getting Out of Sync is a Major Challenge
- 28. Configuration Drift Identical systems gradually diverge over time as theyโre updated Risks of configuration drift: โ Different behaviors in different Environments โ Environment-specific deployment errors โ Overwritten changes โ Impossible to predict how something will behave in production
- 29. โ Systematically propagate changes from development through testing to production โ Accommodate slight differences between orgs (usernames, URL endpoints, etc.) Environment Management The challenge โ Strictly limit the kinds of changes that can be made directly in an environment โ Automate deployments to ensure consistency โ Regularly destroy or refresh development and testing environments โ Automate the creation and setup of development and testing environments The general solution
- 30. Real World Example: Deploying Relational Data Enable release managers to deploy complex relational data easily & reliably between orgs Benefits: Key for Enterprises that deploy complex app configurations like CPQ, CloudSense, B2B Commerce (Cloudcraze), and nCino Test Data requires a relational model with realistic data scrubbed of all PII and sensitive information
- 32. Real World Example: The CI/CD Delivery Pipeline "Our highest priority is early and continuous delivery of working softwareโ - The Agile Manifesto, 2001
- 33. Real World Example: The CI/CD Delivery Pipeline Work is deployed continuously across environments as it is ready and tested
- 34. Version Control โช In general, use Git You can use any version control system you want โช Actively tracking all the work done by developers. Admins are developers too! โช Itโs a very small step from there to automating your deployments โช Automating your deployments opens the door to automating tests and other processes โOffensive Version Controlโ โช Passively capturing (at least) daily snapshots of your metadata to provide some fallback and history โDefensive Version Controlโ
- 35. Branching Strategy โช The following development practices contribute to higher software delivery performance: โ Merging code into trunk on a daily basis. โ Having branches or forks with very short lifetimes (less than a day). โ Having fewer than three active branches. โช Also: โ High performers have the shortest integration times and branch lifetimes, with branch life and integration typically lasting hours. โ Low performers have the longest integration times and branch lifetimes, with branch life and integration typically lasting days. Research from the State of DevOps Reports
- 36. Our Research Teams who integrate more frequently deploy more frequently
- 37. Real World Example: Merge Conflict Resolution โฆ. Simplify merge conflict resolution Interactive conflict editors Resolutions are auto-applied YAML view for XML metadata
- 39. Quality & Testing โ Some amount of our work will be thrown away โ What remains will be tested โ It will either be tested before reaching production โ Or it will be tested by end users On behalf of end users, โ Please test your work!
- 40. This is what the business requested This is what you built Quality has many levels
- 41. Testing is a way of verifying quality โ Fast Tests for Developers โ Static Analysis - Linting โ Static Analysis - Quality Gates โ Unit Testing Developers Need Tests to Give them Fast Feedback on Their Work โ Comprehensive Tests โ Automated Functional Testing โ Code-based Acceptance Testing โ UI Testing โ Non-functional Testing โ Static Analysis - Full Codebase โ Security Analysis โ Performance Testing โ Code Reviews โ Manual QA and Acceptance Testing But we also need comprehensive tests before sending work to prod
- 42. Create connection behaviors in your pipeline Schedule or automate deployments and back promotions. Implement quality gates such as validations, compliance scans or Selenium tests. Real World Example: Continuous Delivery and Quality Gates
- 45. Releasing means exposing functionality to users 1. Releasing by Deploying a. Very straightforward b. Disadvantages i. Deployments must be scheduled ii. Deployments must be coordinated with training and change enablement iii. Deployments are high risk and high stress iv. Rollbacks can be very tricky 2. Separating Deployments from Releases a. Permissions b. Layouts c. Dynamic Lightning Pages d. Feature Flags e. Branching by Abstraction There are many ways of releasing!
- 46. Separating deployments from releases can incur a cost in terms of technical debt If you add complexity to enable features to be temporarily disabled Itโs important to remove that complexity later The Power of Separating Deployments from Releases 1. Dark Deployments a. Deploying during business hours without users noticing 2. Make releases simple 3. Hide work in progress 4. User Acceptance Testing in Production 5. Batch releases to coincide with training/notifications 6. A/B Testing a. This is common practice in marketing b. Experiment, see what works best 7. Canary Deployments a. Releasing to a small group of users to assess impact 8. Easy Rollbacks The Cost of Separating Deployments from Releases
- 47. Start Where You Are DevOps is a Journey Salesforce as Source of Truth. Ad Hoc Component Releases Version Control as the Single Source of Truth, Manual Branch Management Releases based on user stories for better collaboration/merging btn multiple developers and teams Automate manual tasks to scale your delivery and increase efficiency Continually release changes all the way to production for a faster time to value Take a long-term, patient view โ Understand your processes using Value Stream Mapping โ Benchmark your current state using the four Software Delivery Performance Metrics โ Get the basic foundations in place (user story management, version control, delivery pipeline) โ Identify your current constraint (what limits your flow of quality work) โ Eliminate that constraint โ Rinse and Repeat
- 48. Trusted by the Global Leaders 15X 7,086,748
- 49. 100% SALESFORCE NATIVE INTEGRATION DevOps Orchestration Proxy Agent Merge Engines Security / Auth (OAuth 2.0 support) Process Builder Webhooks Job Scheduling Global Find & Replace Alerts & Notifications Dashboard and Reports Salesforce APIs Prod Environments Profiles Permission sets Page Layouts Roles Metadata XML Updated Continuously SECURITY & COMPLIANCE Salesforce Platform Security All major certifications: ISO, SOC, HIPAA, GDPR, Truste. Secure API-based architecture Encrypted credentials OAuth Support / SSO-enabled Secure access to repository On-premise or cloud repositories User access controls Compliance hub Configurable compliance rules Exception reporting with Alerts Data Backup & Recovery Business Continuity Disaster Recovery PREBUILT INTEGRATIONS Agile Planning Tools IDEs 3rd Party CI/CD Tools Monitoring Testing AI/Analytics Security/Compliance NATIVE SFDC EXPERIENCE Lightning UX Native Dashboards Einstein Analytics Salesforce Mobile Salesforce Flow Chatter Collaboration Workflows and Alerts Dev/Test Environments Real World Example: Native CI/CD DevOps Platform for Salesforce DEPLOY Pipelines Deployment Rollbacks Data Management 100% Version Controlled RELEASE Dynamically Assign Permissions Release Dashboard Continuous Integration SALESFORCE DEVOPS 360 Innovation Performance Metrics CI/CD Dashboards and Reports Real Time Monitoring and Alerts Team Benchmarking Continuous Delivery COMPLETE CI/CD PROCESSES PLAN Agile Planning Tools Metadata Tracking CREATE Metadata Tracking Environment Management VERIFY Static Code Analysis Selenium Recorder Apex Tests Metadata Validation Manual Test Scripts Pull Requests
- 50. Questions? Get a Copy of Salesforce DevOps Report Get a Personalized Salesforce DevOps Assessment go to copado.com
- 51. Enterprise Security & Compliance for Salesforce DevOps Secure Architecture โ Secure Platform & Application Architecture โ built on Salesforce / Heroku platform โ Secure communications using oAuth (v2.0) and multiple layers of runtime authentication โ Single-Sign-On (SSO) Support and Secure, encrypted credential storage & access Secure Communications and Access โ Securely access your repositories on-premise or in the cloud (with multiple access levels) โ Full control over user provisioning & access controls Audit Trails, Backup & Recovery โ Enterprise-class Data Backup & Recovery โ Logging & monitoring all security and access events Meeting Security Standards โ Received certifications for all major standards: โ EU-U.S. and Swiss-U.S. Privacy Shield โ ISO 27001/27017/27018 โ Service Organization Control (SOC1,2,3) โ TRUSTe, Payment Card Industry (PCI) โ HITRUST, GDPR, FedRAMP, HIPAA, IRAP Policies and Systems โ Annual security reviews and penetration testing โ Formal Change Mgt, Incident Mgt, SDLC processes & formal Corporate Security Policy โ Enterprise-class Business Continuity & Disaster Recovery Compliance โ Industryโs 1st & only Compliance Hub for SF DevOps โ Set Compliance rules with exception alerts
- 52. What is Continuous Integration? (CI) is the process of integrating and testing the work of all developers and teams on an early and ongoing basis, at least daily Benefits โ Find errors as early as possible โ Reduce integration problems โ Avoid compounding errors Solutions: โ Next Gen CI Pipelines โ Prebuilt Repository Integration โ Metadata Selection Grid โ Advanced Branch Management โ Conflict Resolution โ Integration Analytics New Winter โ20 New Winter โ20 COPADO CONTINUOUS INTEGRATION
- 53. Next Gen CI Pipeline Manager Process collaboration drives faster development times Realtime Pipeline Visualization Simplified Submit Fine Grained Testing Rules Scheduled Back Deployment
- 54. Automatic Merge Conflict Resolution โฆ. Increase your team collaboration Reducing the amount of overwrites. Use the DX Source File format Updated our metadata grid Easier to digest all your metadata. 1, 2, and 3 Panels
- 55. What is Continuous Delivery? โGet changes of all types including new features, configuration changes, bug fixes, and experiments into production and in the hands of users, safely and quickly in a sustainable way.โ Jez Humble, author of Continuous Delivery Benefits โ Ensure every change is releasable โ Increase release velocity โ Improve release quality and security Solutions โ Next Gen CD Pipelines โ Auto Deploy โ Quality Gates โ Smart Behaviors โ Continuous Verification โ Advanced Data Deploy โ MD Fast Lane โ Delivery Rollbacks โ Audit Trails โ Delivery Analytics New Winter โ20 New Winter โ20 New Winter โ20 New Winter โ20 New Winter โ20 COPADO CONTINUOUS DELIVERY New Winter โ20
- 56. Auto Deploy - Automated and scheduled Deployments and Back promotions Quality Gates - Automated tests and manual approvals using quality gates Smart Behaviors - Default behaviors with overrides as needed MD Fast Lane - Specification of which Metadata to expedite and which to inspect Next Gen Pipeline View on the movement of changes through the pipeline New Copado Continuous Delivery
- 57. Dynamic Pipeline Editor Two Clicks to Take Any Action Hover to Get More Detail Next Gen CD Pipelines
- 58. Advanced Data Deploy Enable release managers to deploy complex relational data easily & reliably between orgs ADD is broken out into 3 components 1. Data template editor 2. Data deployment wizard 3. Advanced Data Step Benefits: Key for Enterprises that deploy complex app configurations like CPQ, CloudSense, B2B Commerce (Cloudcraze), and nCino Test Data requires a relational model with realistic data scrubbed of all PII and sensitive information The existing Copado data feature requires high technical knowledge to manually create relational queries and understand the data model of the records theyโre migrating. This feature now makes it easy for you to manage instead.