Skip to main content

On our development system, our standard application is developed in a layered branch model. Developed software is deployed to various customers using a CiCd pipeline. To achieve this we regularly create software code on the development system that must be executed on the development system but may never be executed on a customer system.

These software parts should never be included in a deploy package.

 

We want to be able to model in SF that certain parts of code should not be part of a deploy package. In this way, developers are triggered on the choice to be made.

This is a much more elegant and less error-prone solution than including protections in the software itself.

This prevents errors and damage to customer systems.

 

NewOpen