Define project dependencies#

  1. Open a project’s dependency management view.
  2. Select the upstream project and required state.
  3. Save, then inspect the upstream/downstream relationship in the summary.
  4. Verify the relationship describes a real prerequisite. Remove obsolete dependencies through the available action.

Dependencies gate delivery order. They do not transfer manifests or automatically merge two projects into one application. Avoid circular relationships and inspect validation errors before saving.

Preview a promotion#

  1. Open the environment matrix or a retained release’s promotion entry.
  2. Choose the source release and an eligible destination project/target.
  3. Run the promotion preview. Inspect the source commit/artifact relationship and destination-specific changes.
  4. Resolve scope, target, policy or dependency failures before creating the promotion.
Choose a destination from the environment view to begin a promotion preview. Review that preview before explicitly creating the promotion.
Choose a destination from the environment view to begin a promotion preview. Review that preview before explicitly creating the promotion. View full size ↗

Create and follow the promotion#

Create the promotion only after reviewing the preview. Open the resulting promotion and child run records. Follow each destination’s plan, approval, execution and verification. A created promotion record means orchestration was requested; it is not proof that all destinations are deployed.

A promotion should preserve the intended release provenance while applying destination-specific configuration. Do not assume it means “deploy the latest branch tip” or that a source environment’s approval automatically approves the destination.

Recovery#

If one destination fails, inspect that destination’s run and live state. Determine whether subsequent work is blocked by dependencies or already started. Use the run’s offered retry, rollback or reconcile actions; do not recreate the entire promotion blindly.