Domino enables you to manage environment inheritance and revision lifecycles with build propagation, revision pinning, and revision selection. These tools help ensure the automatic propagation of environment updates, allowing for safe testing of changes, and giving you control over which revisions are used across your workflows.
This approach improves environment lifecycle management in two key ways:
-
Better governance and compliance, since environment updates can be cascaded through derived environments.
-
More robust automation, with the ability to test updated environments before production workloads adopt them.
Together, these capabilities make it easier to scale, standardize, and maintain reliable environments across teams and projects.
-
You must have permission to create or edit compute environments.
-
You should be familiar with how base and derived environments work in Domino.
When creating or editing an environment:
-
Go to Environments > Create Environment or open an existing one.
-
Under Base Environment, select a base environment.
-
In the Revision dropdown, you can:
-
Choose a specific revision of the base, or
-
Select Active - auto-rebuild to subscribe to the base’s current Active revision.
-
Choosing Active - auto-rebuild enables build propagation. Any change to the Active revision of the base environment will trigger an automatic rebuild of this environment.
You can control whether the latest revision becomes Active automatically or if activation must be manual.
When creating a new environment:
-
In the setup form, check or uncheck Auto-assign latest revision as Active:
-
Checked: New revisions are automatically set to Active.
-
Unchecked: You must manually activate revisions (i.e., the Active revision is pinned).
-
For existing environments:
If using build propagation, uncheck this option to avoid automatically activating new, untested revisions:
-
Go to the Revisions tab.
-
Uncheck Auto-assign latest revision as Active to pin the current Active revision.
-
Manually promote future revisions when ready.
If you selected Active - auto-rebuild in Step 1:
-
Any time the base environment’s Active revision changes, a new revision of your environment will be built automatically.
-
If revision pinning is off, this new revision becomes Active.
-
If revision pinning is on, the new revision must be activated manually.
This supports chained propagation across multiple levels of environment inheritance.
-
Domino Standard Environments describes the pre-configured environments that come with Domino.
-
Create a Domino Environment using an existing environment or start from a custom setup.
-
Edit an Environment to enable tools, run scripts, or manage environment variables.
-
Set default Environments establishes a starting point for all new projects or an environment for a specific project.