Downloaded 12 times
More Related Content
Similar to Gear up for Continuous Integration with Salesforce DX, Circle CI and Clayton
Gear up for Continuous Integration with Salesforce DX, Circle CI and Clayton
- 1. #ForceAcademyLA Gear up forContinuous Integration with Salesforce DX, Circle CI and Clayton
- 2. #ForceAcademyLA Thank you Sponsors! ABig shout out to our sponsors, without them these events would not be possible:
- 3. #ForceAcademyLA#ForceAcademyLA Hello! DANIEL STANGE Technical Architect die.interaktivenGmbH & Co. KG Found Salesforce boring in the dark ages - Changed my mind. Frankfurt, Germany User Group Leader You can find me at: @stangomat https://www.linkedin.com/in/daniel-stange- 08474a49 https://trailhead.com/me/stangomat Blog: blog.danielstange.de
- 4. #ForceAcademyLA Let’s start CIfrom scratch!
- 5. #ForceAcademyLA ➜What do youneed? ➜Why CI? ➜Basic Concepts ➜Design our workflow ➜Run our workflow ➜Add some QA measures ➜Next Steps AGENDA
- 6. #ForceAcademyLA Clone my demorepo if you want to work along github.com/dstdia/ForceAcademy18
- 7.
- 8. #ForceAcademyLA PREREQUISITES * Whatdo you need to start? ➜ Salesforce DX Developer Hub (your Prod or a trial dev hub org) ➜ A distributed version control system. Github or Bitbucket are great ➜ The Salesforce CLI (part of Salesforce DX)
- 9.
- 10. #ForceAcademyLA WHY CI? Extra effortto save some time and effort? ➜ Structured Change Process: Repeatable, automated, transparent ➜ Find bugs and flaws ➜ Deploy more often and earlier ➜ Reduce the effort to collect and deploy changes ➜ Reduce deployment failures ➜ Promote agile / iterative approach ➜ Introduce QA steps
- 11. #ForceAcademyLA WHY PUT THEEFFORT IN A CI WORKFLOW Test Automation Deployment Automation Development Lifecycle
- 12. #ForceAcademyLA WHY SFDX, CircleCI, Clayton? ➜ SFDX is the new default toolchain to manage Salesforce customizations ➜ Circle CI and Clayton.io integrate seamlessly by SSO with Bitbucket or Github… ➜ the entry tier is free ➜ (relatively) easy to configure
- 13.
- 14.
- 15. #ForceAcademyLA First Steps ➜ Checkoutmy repo from http://bit.ly/DSTFA18-Code ➜ Sign up for a CircleCI trial: https://circleci.com/ (single sign-on with Github or Bitbucket) ➜ Sign up for a Clayton.IO trial https://getclayton.io (single sign-on, again)
- 16. #ForceAcademyLA ORCHESTRATION sfdx force:org:create sfdx force:source:push sfdxforce:apex:test:run sfdx force:source:convert sfdx force:mdapi:deploy ➜ Create an org ➜ Install your source ➜ Run tests ➜ Convert to Metadata format ➜ Deploy to target
- 17.
- 18.
- 19. #ForceAcademyLA SLEEVES UP! We’re gettingour hands dirty
- 20. #ForceAcademyLA#ForceAcademyLA HANDS ON –Choose your path ➜ Advanced Path: Work along while I demo ➜ Easier Path: Use the Cheatsheets in my repo’s wiki to copy&paste: http://bit.ly/DSTFA18-Wiki ➜ Easiest (or troubleshooter): ➜ Just read and along in the code, then make a commit into master and check the results
- 21. #ForceAcademyLA#ForceAcademyLA HANDS ON –What you will need ➜ A self signed certificate and a connected app in your dev hub and all deploy targets ➜ Read how to do it here: http://bit.ly/SFDXCert
- 22.
- 23. #ForceAcademyLA#ForceAcademyLA Building our flow:STEPS ➜ Clone my repo: ➜ https://github.com/dstdia/ForceAcademy18 ➜ Sign up and Connect to Circle CI
- 24. #ForceAcademyLA#ForceAcademyLA Building our flow:The DX setup job ➜ Understand the Structure of the Jobs-Section ➜ Download and install Salesforce DX ➜ Authenticate your Org ➜ Create and Persist a Workspace
- 25.
- 26.
- 27.
- 28. #ForceAcademyLA#ForceAcademyLA Remember… ➜ Jobs runin independent containers. You have to persist what you want to use later… ➜ You’ll have to export paths to your containers later ➜ You can use caches and folders to store artefacts
- 29. #ForceAcademyLA#ForceAcademyLA Building our flow:The Test Execution job ➜ Create a new scratch org ➜ Checkout source ➜ Push Source to test org ➜ Execute the Apex Unit Tests ➜ Persist the Results ➜ Can you add Lightning Testing Service on your own?
- 30.
- 31.
- 32. #ForceAcademyLA#ForceAcademyLA Building our flow:The Deployment job Typically you will need a Sandbox or Production Org to deploy to. We can use a scratch org here. Feel free to use an existing DE or Sandbox instead. ➜ Convert Source to Metadata API format ➜ Deploy Metadata
- 33.
- 34. #ForceAcademyLA#ForceAcademyLA Bringing it alltogether – the Workflow Section Use filters and requires to control ➜ order ➜ parallelism ➜ conditions of the workflow execution
- 35. #ForceAcademyLA#ForceAcademyLA DONE! ➜ Make achange and commit to your repo… ➜ But don’t push yet…!
- 36.
- 37. #ForceAcademyLA#ForceAcademyLA Running our flow:STEPS o Now push your commit to origin o Extra: Make any other change you like. o Review your CircleCI workflow – did it complete? Can you fix the error if you get any?
- 38.
- 39. #ForceAcademyLA Using static codeanalysis as Quality Gate ➜ Static code analysis checks your code/metadata against pre -defined rules ➜ Clayton is Salesforce specific, engine is built to “understand” the context of your code ➜ Clayton ”talks” to your CVS ➜ Violations appear as errors and can be used to block merges ➜ Can be used in addition to or instead of local static code analysis like PMD / ApexPMD
- 40. #ForceAcademyLA#ForceAcademyLA Quality Gates: STEPS ➜Sign up for Clayton.io ➜ Connect your repo for a code review ➜ Set up rules
- 41. #ForceAcademyLA#ForceAcademyLA Quality Gates: TRYIT OUT ➜ Modify the Sample Class to violate your Clayton rule set ➜ add DML in a loop ➜ Or an empty method ➜ Or a badly named method (like Badly_namedMethod() ) ➜ Commit & push ➜ Check the Clayton results ➜ Review your commit in Github / Bitbucket
- 42.
- 43. #ForceAcademyLA#ForceAcademyLA NEXT STEPS ➜ Breakdown monolythic metadata ➜ use 2nd generation packages to have smaller installable bundles ➜ Parallelize jobs to save time ➜ Handle test results and failures
- 44. #ForceAcademyLA#ForceAcademyLA Thank Y u! Anyquestions? You can find me at: @stangomat Daniel.stange@die-interaktiven.de Code at github.com/dstdia/ForceAcademy18