#Impact salesforcesaturday copado - session -2 by Hariprasath

Information about #Impact salesforcesaturday copado - session -2 by Hariprasath

Published on June 24, 2020

Author: hariss63

Source: slideshare.net


1. New Delhi Salesforce Developer Group #ImpactSalesforceSaturday Functionalities of Copado -Hariprasath Thanarajah - Senior Salesforce Developer LEARN . SHARE . CELEBRATE . SALESFORCE

2. About Me: Hariprasath Thanarajah ● Senior Salesforce Developer @ Wiley ● Copado MVP ● 4 X SF Certified and 2 X Copado Certified Developer ● Salesforce Analytics Champion https://www.linkedin.com/in/hariprasath-thanarajah-5234b660/ @hariss63 https://trailblazer.me/id/hthanarajah

3. New Delhi Salesforce DG • First Revival Meetup in February 2016 • Twitter: https://twitter.com/newdelhisfdcdug • Hashtag: #ImpactSalesforceSaturday • New Delhi Salesforce DG Trailblazer Community Group: http://bit.ly/NewDelhiCommunity • Website: https://newdelhisfdcdug.com

4. Mentorship Central • We are dedicated to matching Mentee's seeking specific Salesforce goals with Mentors. • Sign up as a Mentor or Mentee and connect with other Mentors/Mentees • http://bit.ly/SFMentorshipCentral

5. Aim : To understand what is Copado in terms of Salesforce DevOps. Prerequisites : Nothing specifically , But better to know the basics. • Salesforce basics – About Salesforce Organizations. • Git Basics (Optional) • Salesforce Deployment processes.

6. What is Copado? Copado is the #1 DevOps tools native to Salesforce that helps Admin, Developers, Release Managers, and the Product Owners to deliver the feature in a faster and secure manner to the market.

7. Copado Architecture Copado enables you to Operate Salesforce Faster with More Trust

8. Copado Architecture Copado Back End

9. - An Org Credentials is a key element to how Copado Works. It represents a User’s access to a Salesforce environment for Copado. - It is key that the first Org Credential needs to be validated is the one that connects the User to the Organization where Copado is installed. - Org credentials can be created per user, or we can have shared Org Credential which can be marked as “Default” org credentials. - Every org that needs to be accessed through Copado needs to have at least one Org Credential. - We can create a set of Default org credentials that are later shared with the team to use with Copado. Org Credentials

10. - An Environment is non other than a Salesforce Organization. Environment records are created automatically when the first Org Credential related to that Salesforce Org is authenticated. - The Organization ID will be the external ID and an environment can have multiple Org Credentials related to it. - Also we can define different Apex Test behaviors in the Environment record, - Enforcing Copado to run all local tests when deploying to this environment. - Modify the Minimum Apex Test Coverage. Environments

11. - The Git Repository record represents the relationship between Copado and the Version Control System which we are using to maintain the history of our metadata. This record is a critical element of the setup and is required to enable Copado to synchronize and run the git operations. - It will store the Authentication between Copado and the VCS Repository (In this case the GitHub repository). - There is a One-to-One relationship between the repository and a Pipeline. This needs to be considered when creating a new pipeline. Git Repository

12. - A Git snapshot record represents the relationship between a Salesforce Org (through an Org Credential) and a Git Branch. Copado can dynamically identify which branch in Git is related to which Salesforce Org from the Org Credential which is linked to the Git snapshot record when running the commit and merge operations. - It allows to take a backup of a Salesforce environment’s metadata and commit that into a corresponding Git Environment Branch. - So Git Snapshot is the child to, - Git Repository – It represent the environment branches of a Git repository. - Org Credentials – It identify which Salesforce environment is related to a Git environment branch. - It is also used to initialize the master branch in the Git Repository with all the metadata folders and files present in your Salesforce Production Environment. Git Snapshots

13. - A Pipeline is also known as Deployment Flow where we connect a list of Environments defining a structured path in which our Salesforce metadata changes are going to move through, typically from the lower environments to Production. - It works as a traffic-control system for ongoing changes and releases. Also, it allows us to, - Visualize the path to Production. - Information about the remaining US’s to be deployed to upper env and lower env. - The last deployment status per environment. - Each Environment in a Pipeline can have multiple sources, but it cannot have multiple destinations. Pipeline

14. - Projects are the parent-level object used to group together the User Stories which means the work items for the Developers and Admins. - This is significant for the DevOps processes because all of it’s related works (US’s) need to be follow the same pipeline which means a defined deployment path. - The project record needs to be linked with the pipeline to detect the deployment flow to deploy the changes. - For DevOps processes in Copado, every User Story: - Must be linked to a project to identify the pipeline. - Must have a title. - Must be assigned to an Authenticated org credentials in the project’s pipeline. Project

15. - User Stories are the central piece of how Copado works, because most of the daily activities that Admins and Developers will do in Copado revolve around User Stories. - The US identifies its deployment path through the Project/Pipeline relationship. Also we can have a visual path in the US layout. - The recommended fields to maintain and complete are: - Title: Not technically required though it allows you to identify the User Story purpose. - Project: technically required to deploy the US. It defines, through the related Pipeline, the deployment flow. - Org Credential: identifies the retrieve access and the environment where the US originated and will be worked. - Environment: will be automatically populated based on the Org Credential. - There are multiple Quality Gates that can be triggered from an US to ensure the quality at the lower environment itself (Apex Tests, validation deployments, Static Code Analysis, Pull requests of the changes, etc.). User Story

16. DEMO - First Deployment Using Copado GO THROUGH THE PLAYGROUND

17. • Signup to Copado Community - https://success.copado.com/ • Signup to GitHub - https://github.com/join • Create a Playground to hands-on with Copado. • Copado Community -> Click HELP & TRAINING tab -> MY PLAYGROUNDS -> Create NEXT SESSION • Continue the deployments and will discuss some of the best practices that we need to consider while using the Copado as our DevOps tool for Salesforce. Next Session

18. Follow & Join New Delhi Salesforce DG • Join to know about future events and to RSVP: https://trailblazercommunitygroups.com/delhi-in-developers-group/ • For all the content: https://newdelhisfdcdug.com • Let’s start conversations on Success Community: http://bit.ly/NewDelhiCommunity • Follow us on Twitter: https://twitter.com/newdelhisfdcdug • Hashtag: #ImpactSalesforceSaturday • Follow us on Facebook: https://www.facebook.com/newdelhisfdcdug

#impactsalesforcesaturday presentations

Related presentations

Other presentations created by hariss63