Packages and Releases

Packages and Releases are the essential elements of automation workflows in the Chassy Console

Packages

In Chassy, a package is an immutable reference to any application artifact imported/published to our storage platform (Chassy Index). These artifacts may be executables like binaries or containers, arbitrary files, archives, and much more. When packages are available in Chassy, they can then be used within a workflow as part of a Release intended for deployments to machines or executed directly on machines as a way to issue commands.

A package cannot be deployed without being included in a release.

Packages are imported during the execution of a workflow using the Import Package Step.

While Chassy does not impose any versioning philosophy, we generally recommend following semantic versioning for packages when possible. Packages may be associated with arbitrary version strings which can be queried and used to filter available packages in the Chassy Index.

Releases

A release is a versioned bundling of one or more versioned packages intended to be deployed to machines belonging to a particular Chip in a Fleet. Releases can be created using the Release step in the workflow engine. A release can then be deployed to a fleet using the Deploy step.

All releases in Chassy must follow the semantic versioning (semver) scheme. Manual versions can be specified directly or Chassy can generate compliant version numbers based on certain constraints you specify automatically.