Principles
Current Principles followed by [email protected] Practitioners
Any aspect of code or config that gets deployed (not applied directly) into a Salesforce org should be traceable to an artifact built from a point in time from a source code repository. The artifact should have a name, version number and an associated lifecycle.
[email protected] projects will strive to improve developer productivity by ensuring ease of usability for these practices and frameworks.
Every [email protected] Practitioner will follow a concept of build/deployment budget. They will look to minimize the duration of which a feature branch lives and strive to do whatever they can to keep these attributes in check across their packages.
[email protected] Practitioners will design their modules in such a way that it reduce the inter-dependencies, facilitate integration, deployment and test.
Recurring manual steps hampers the path to production by making it unaffordable to deploy at will. This is one of the major reasons why Salesforce deployments are infrequent and batched together. [email protected] practitioners will remove any such recurring manual steps, by designing the code or config around it or introduce automation using a variety of techniques.
Technical debt can arise in various forms. It can be a functional element that can be realized differently or short cuts that have taken to release a feature. [email protected] emphasizes technical debts will always be prioritized along with other development and due care will taken to mitigate it.
Artifacts, run books, and release notes are fundamental tools to enable complete visibility to changes in the environments. Ensure the team adheres to the DevOps governance process and configuration changes outside the deployment pipeline are documented consistently to refer to historically as needed.
Last modified 1mo ago