Book Image

Salesforce Lightning Platform Enterprise Architecture - Third Edition

By : Andrew Fawcett
Book Image

Salesforce Lightning Platform Enterprise Architecture - Third Edition

By: Andrew Fawcett

Overview of this book

Salesforce Lightning provides a secure and scalable platform to build, deploy, customize, and upgrade applications. This book will take you through the architecture of building an application on the Lightning platform to help you understand its features and best practices, and ensure that your app keeps up with your customers’ increasing needs as well as the innovations on the platform. This book guides you in working with the popular aPaaS offering from Salesforce, the Lightning Platform. You’ll see how to build and ship enterprise-grade apps that not only leverage the platform's many productivity features, but also prepare your app to harness its extensibility and customization capabilities. You'll even get to grips with advanced application architectural design patterns such as Separation of Concerns, Unit Testing and Dependency Integration. You will learn to use Apex and JavaScript with Lightning Web Components, Platform Events, among others, with the help of a sample app illustrating patterns that will ensure your own applications endure and evolve with the platform. Finally, you will become familiar with using Salesforce DX to develop, publish, and monitor a sample app and experience standard application life cycle processes along with tools such as Jenkins to implement CI/CD. By the end of this book, you will have learned how to develop effective business apps and be ready to explore innovative ways to meet customer demands.
Table of Contents (17 chapters)

Releasing from source control

Throughout this book, we have been creating packages using the Salesforce DX CLI manually. When you are starting out with a new package, creating packages is arguably a less frequent operation, and you can certainly continue to issue these commands manually, using the preceding pipeline to simply confirm that your code base is stable enough to create a test package (I would recommend you use Git tags for each package version). However, once your number of releases and their frequency grows, you may want to start to add some more automation.

It is possible to automate the Salesforce DX CLI commands related to packaging through the Jenkinsfile. To consider this, though, you must first think about your use of branches within source control and, from that, determine what changes in source control warrant a new package version to be created, and,...