Deploying

The Axon Ivy Engine provides various ways in which Axon Ivy projects can be deployed. We strongly recommend to automate the deployment in a CI/CD pipeline.

  • Engine-Cockpit: In the Engine Cockpit projects can be deployed manually via a user interface.

  • REST-API: Projects can be deployed using our built-in REST API via HTTP/HTTPS. The preferred approach for implementing a CI/CD pipeline.

  • Deployment-Directory: Projects can be installed via the deployment directory using a file-based variant. Very useful to quickly deploy projects manually or as alternative approach for building a CI/CD pipeline.

  • Maven-Plugin: As part of the Axon Ivy Maven Plugin projects can be deployed within a Maven build.

When deploying you need to decide into which application version you want to deploy. You can choose between new and released or an existing application version number.

  • new will create a new application version with the next available version number and will release it.

  • released will deploy to the currently released version. If no version is released yet, a new version will be created and released.

  • <version> will deploy into an already existing version. If the application version does not exist, the deployment will fail.