Skip to Content

(Deployment) Packages

Last modified by Erik Bakker on 2024/02/20 13:55
Error

Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.

In this microlearning, we will learn what (deployment) packages are and how they are included in the eMagiz platform. In a nutshell, the (deployment) package is a representation of a specific flow version within Create including its resources and including a unique set of dependencies (i.e. the build number reference).

Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

  • Basic knowledge of the eMagiz platform

2. Key concepts

This microlearning centers around (deployment) packages.
With a package, we mean: A set of information elements that will ensure that the flow as created works on runtime level

A (deployment) package consists of three parts:

  • A specific flow version, identifiable by the first three parts of the version number (i.e. 1.0.3)
  • The resources that were linked to the flow
  • The set of dependencies that are needed to properly run the flow. This set is identifiable via the build number version (i.e. 57)

As a result:

  • The combination of flow version and build number leads to a unique deployment package version (i.e. 1.0.3.57)

3. (Deployment) Packages

In this microlearning, we will learn what (deployment) packages are and how they are included in the eMagiz platform. In a nutshell, the (deployment) package is a representation of a specific flow version within Create including its resources and including a unique set of dependencies (i.e. the build number reference).

A (deployment) package consists of three parts:

  • A specific flow version, identifiable by the first three parts of the version number (i.e. 1.0.3)
  • The resources that were linked to the flow
  • The set of dependencies that are needed to properly run the flow. This set is identifiable via the build number version (i.e. 57)

As a result:

  • The combination of flow version and build number leads to a unique deployment package version (i.e. 1.0.3.57)

This means that every time you change the flow version eMagiz will create a new (deployment) package that you can include in your Release via the Releases functionality. The same applies when eMagiz launches a new build number. As of that moment, all new flow versions will be packaged with the help of the latest build number. This also leads to a new (deployment) package version.

As said you can deploy all these packages to the correct locations with the help of the Releases functionality. If you need more information on how that works you should revisit the Crash Course Platform to brush up on your knowledge.

Furthermore, eMagiz offers an overview of all (deployment) packages within a release. This overview can be found under Deploy -> Packages. This overview also provides a fallback option to manually install (deployment) packages to the runtime in case the preferred alternative of Releases does not work.

novice-release-management-packages--packages-overview.png

This explanation should hopefully clarify a bit of what happens under the bonnet and how the combination of your flow and the build number work in unison when the solution is deployed.

4. Key takeaways

A (deployment) package consists of three parts:

  • A specific flow version, identifiable by the first three parts of the version number (i.e. 1.0.3)
  • The resources that were linked to the flow
  • The set of dependencies that are needed to properly run the flow. This set is identifiable via the build number version (i.e. 57)

As a result:

  • The combination of flow version and build number leads to a unique deployment package version (i.e. 1.0.3.57)

5. Suggested Additional Readings

There are no suggested additional readings on this topic.