In this approach, the out-of-the-box CI / CD features provided by the BPM Suite 6 product are utilized.

This reference architecture is particularly relevant to those with experience with other BPM products that also provide native support for continuous integration and delivery.

Highlights of this BPMS Driven Delivery approach include:

1. Developers and business analysts collaborate on the same BPM Suite environment.

2. The managed repository feature from BPM Suite is utilized .

3. System of truth of version controlled BxMS artifacts is the .niogit repository of BPM Suite .

Details can be found in the BPMS Driven Delivery README.

In this approach, Jenkins is utilized to orchestrate CI / CD workflows of BxMS business processes and rules.

This reference architecture is particularly relevant to software developers already proficient with (and have an appreciation for) Jenkins and hosted Git repositories (such as Github or Gitlab).

Highlights of this Jenkins focused approach are as follows:

1. Master branch of BPM projects is always in a deployable state.

2. Can be fully automated (as per principals of Continuous Delivery and DevOps)

3. System of truth of version controlled BxMS artifacts are the repositories managed in a custom GitLab environment.

4. Every developer has their own local BPMS instance.

Details can be found in the BxMS CI / CD using Jenkins README.

In this approach, Jenkins and GitLab continue to be utilized to orchestrate CI / CD workflows of BxMS business processes and rules. Additionally, the Git Flow approach is leveraged.

Highlights of this Git flow approach are as follows:

1. Not fully automated.

2. Makes heavy use of git branching.

3. Developers never work on master.

4. Requires git branching capabilities of BPM Suite.

5. System of truth of version controlled BxMS artifacts are the repositories managed in a custom GitLab environment.

6. Every developer has their own local BPMS instance.

Details can be found in the Git Flow Model README.