Product delivery

Linked products

Split a workflow into products that depend on each other.

Large workflows are easier to own as several products: for example a shared reference-data product that other operational products build on. A version declares the upstream products it needs, by major version.

Declare a dependency

In the New version dialog, under Linked products, pick the upstream product and its major version. Converge refuses:

  • a product depending on itself;
  • a major version the upstream product never published;
  • a dependency that would create a cycle.

Install order

An upstream product must be installed in the same project first, at the major version the dependent was packaged against. Installing the dependent before its upstream is refused with a message naming the missing product. Product groups install a whole set in the right order for you.

Breaking changes

A new major version of an upstream product is a breaking change. Upgrading an upstream install across a major version is refused while a dependent in the same project has no version built for the new major. Publish a new version of the dependent against the new major first; the upstream upgrade then succeeds and reports which dependents to upgrade next.

Converge