Environment versus classification node groups
Environment node groups assign environments to nodes, such as test, development, or
production.
A node can belong to only one environment node group. If a node is
added to more than one environment group, classification errors occur. See this classification conflict article for more
information.
Each environment node group:
- Must correspond to a Git branch in a control repo you want to use for targeted code deployments. The Git branch and environment group must have the same name.
- Must be a child of the All Environments node group (or whichever is the highest-level environment node group in your installation). Furthermore, your environment node groups, themselves, must not have any child groups, except one-time run exception subgroups used for canary testing.
- Must not include classes or configuration data.
Classification node groups assign classification data to nodes, including classes, parameters, and variables. A node can belong in more than one classification group.
Each classification node group:
- Must be a child of All Nodes or another classification group.
- Must not be specified as an environment group in the group metadata.
