Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • If the project containing the Pipeline has private SnapPacks, then those Snap Pack versions are used. Otherwise, the Snap Pack corresponding to the snap Snap distribution is used.

  • If the JCC node is on new Snaplex version, the new SnapPack versions are used.

  • If the JCC node is on a previous Snaplex version, then the previous versions of the SnapPacks are used.

Order of Snap Version Reference

  1. Private SnapPack version in a project where the Pipeline is located.

  2. Private SnapPack version in project space shared folder

  3. Private SnapPack version in Org-level global shared folder

  4. The Snap version configured in the distribution (stable/latest) used by the Org. The Org-level version overrides are applied here.

A private SnapPack version always takes higher precedence over the configured Org-level SnapPack.

...

During the five-week window for Snaplex auto-upgrade, Snaplex instances could be in one of three states.

  • All

...

  • Snaplexes are on

...

  • the previous Platform version

...

  • --->Design-time

...

  • Snap catalog uses old

...

  • Snaps

  • Mixed Versioned

...

  • Snaplexes include some

...

  • Snaplexes are on the previous Platform version and some are running on new

...

  • version--->Design-time Snap Pack Catalog uses old snaps

  • All

...

  • Snaplexes on

...

  • new platform version

...

  • --->Design-time

...

  • Snap Pack catalog uses new snaps

So until all Snaplex instances are upgraded to the new version, the design-time Snap Pack Catalog will use the old Snap Pack Catalog. If one Snaplex is switched back to the previous Snaplex version after the upgrade, the catalog again reverts to the previous version.

...