Environments

Updated 2 months ago by Iván Minaya

Environment records are created automatically when Org credentials are authenticated. The Organization ID will be the external ID. This way an Environment may have multiple Org credentials, different users, to the same Organization (aka environment)

By default the environment name will get the Org credential name upon creation, but it can be updated afterwards.

Change the default minimal code coverage, it will enforced on the User Stories as part of the Copado Change Management module.

Enforce all local apex test execution across the entire Copado application whenever a deployment is done to the environment regardless of the Org credential used or the user selection on the deployment record. This can be used to replicate the same behaviour on sandboxes as in Production

Environment Variables

Environment Variables allow users to make Commits, Deployments, Branch Validation and Selenium Test Cases environment agnostic. 

Click here for more information.


How did we do?