A healthy code state
Ensuring a healthy code state is important when it comes to any development. By healthy code state, we mean that the code components (plugins, custom components (PCFs), and web resources) that get deployed to the downstream environments should be in a ready state.
Usually during the implementation, a developer deploys versions to the development environment that aren’t ready to be released to the downstream environment yet.
In addition, there are two reasons why we would like to achieve a healthy code state:
- The developer could forget to deploy the latest working version to development after the implementation is completed
- Solutions to contain the binaries (
.dll
files) should not be checked into the repository
In this section, we will take a look at one approach to how we can make sure that we only deploy the correct version of pro code components.
There are at least two different approaches:
- Map files: We will take a...