This content is dedicated to our next version. It is work in progress: its content will evolve until the new version is released.

Before that time, it cannot be considered as official.

Bonita CI/CD suite

The BCD Deployer, as the technical artifact for Bonita CI/CD suite in Bonita, is deprecated and being phased out. As of September 2023, the BCD Deployer is no longer receiving updates or improvements, as it is being replaced. The CI/CD pipeline now relies on the Bonita LA Deployer, which is described hereafter and does not require a separate Docker container. Access to the Bonita LA Deployer is included in the contract as part of the Bonita CI/CD suite offering (formerly the BCD offering).

To meet diverse customer environments and DevOps strategies, our BPM solution supports two deployment models:

  • Application Deployment: For environments where the BPM platform is already provisioned, only the business application layer is updated—ensuring quick, lightweight deployments.

  • Full Deployment: A complete bundle of the BPM platform and application is delivered together, ready to run on any target server even if no prior installation exists.

This flexibility makes it easy to adapt deployments to your infrastructure and governance needs.

Bonita CI/CD suite lets you build a Living Application from source code in a repository and deploy the generated artifacts, all from the command line.

These deployment modes are illustrated in the diagram below to help visualize their architecture and usage.

This section presents the overall concept, please refer to the product documentation or contact Bonitasoft for implementation details and best practices.

Application Deployment

The BPM platform is already installed. Only the application artifacts (process definitions, user interfaces, scripts, connectors, etc.) are updated or redeployed. This is an incremental deployment model.

Bonita Continuous Delivery Capabilities

Self contained Application Deployment

In this mode, a Bonita project is build into a single binary (image or Tomcat bundle) packaging the platform and the application code together. A new deployment is required for each new version of the project. In this scenario all artifacts updates are done at startup.

Bonita Continuous Delivery Capabilities

Basic concepts

Bonita CI/CD suite offering (formerly BCD offer) has evolved now into two Java command-line interfaces (CLI) which allow to build and deploy Bonita Living Applications. You will be able to download the latest versions of the CLIs from our Bonita Artifact Repository and then integrate the execution in your developer and CI pipelines.

Bonita CI/CD suite features do not require docker anymore. Usage is therefore greatly simplified. The only remaining prerequisites are Java and Maven installed on the host running the CLIs.

Highlight

What’s new in BCD? Find out what’s new in Bonita Continuous Delivery !

Start building Check out how to build a Living App repository.

Start deploying Check out how to deploy a Living App.

For both CLIs you can have a look at the exec-maven-plugin to include build and/or deploy step in the bonita project build lifecycle. (starting from version 7.13.x, a bonita project is a maven project)
Currently you should consider the maven aspect as a black box, because the studio perform some instrumentation of the project’s pom.xml file, but advanced users can still take advantage of the maven aspect of the project.