CI pipelines in Salesforce can save a huge amount of developers’ time which otherwise would be spent managing this process. They also help to prevent a lot of mistakes related to deploying the changes.
We’re going to have hands-on experience on how to successfully create and deploy CI pipelines, reduce manual work and eliminate human error to build a more effective solution. Moreover, we are going to explore some of the options based on typical requirements and processes.
2. #CD22
● Introduction
● About Continuous Integration (CI)
● CI platforms
● About SFDX and scratch orgs
● Benefits of using CI
● GitHub Actions
● Authentication
● Demo
● Alternatives.
● QA
Agenda
5. #CD22
1. Helps detect conflicts quickly.
2. Makes the deployment process faster.
3. Help keeping different environments in sync.
4. Formatt Code.
5. Boosts security.
6. Makes roll-back process easier.
7. Improves code quality by automated code scanning and testing.
Benefits of using CI
6. #CD22
● GitHub Actions
● Circle CI
● Jenkins
● GitLab Pipelines
● Bitbucket Pipelines
● TravisCI
CI Platforms
12. #CD22
1. .yml file construction.
2. Create a simple pipeline in GitHub.
3. What can be done with .yml file configurations.
4. Create new branch, push changes and show how new pipeline is
started and run on the scratch org.
5. Commit changes and let CI run tests.
Demo
17. #CD22
GitHub Actions documentation:
https://docs.github.com/en/actions
Simple step-by-step guide:
https://www.salesforceben.com/how-to-build-a-ci-cd-pipeline-for-salesforce/
CI by Gearset:
https://docs.gearset.com/en/articles/605227-continuous-integration
https://medium.com/@maheshchouhan1995/ci-cd-using-gearset-309332ae8a9c
Best practices:
https://www.copado.com/devops-hub/blog/salesforce-ci-cd-best-practices-build-run-test-cddd
About CI:
https://www.qentelli.com/thought-leadership/insights/continuous-integration
Links and sources: