Summary
In this chapter, we’ve looked at packaging as a technique for deploying our code changes and compared the different types of packages available. For each type of package, we have seen the steps required to bundle our Salesforce changes into those packages for further distribution.
We’ve also seen that these changes can follow a source-driven DevOps process if we select the appropriate type of package. Packaging by no means replaces DevOps processes; rather, it is a technique that forms part of DevOps on the Salesforce platform. Equally, it is not the only means of delivering your changes for scenarios outside of the ISV Partner space.
In the next chapter, we’ll start looking at bringing all the elements of our source-driven workflow together and adding some automation as we investigate the CI/CD automation of our processes. This represents an alternative delivery mechanism for our changes that doesn’t require packaging.
