Download
  Contact us

Best Practices for Continuous Integration with Bonita BPM

01 Apr 2016 - Mickey Farrance

Already considered a mainstream approach in software development projects, Continuous Integration is just as important when developing  BPM applications. Here’s what we recommend.

1. Maintain a single, “version controlled” source repository

Keeping process design changes locally on developer’s laptops is risky, hinders collaboration and leads to high tension during the integration phase – when it is not certain that all the fragments will come together successfully. Leverage the Subversion integration available in Bonita BPM Studio to connect and synchronize your processes being developed with a centralized version controlled repository.

 

2. Frequently commit process design changes

The longer a developer keeps changes on a local machine, the higher the chance of running into a conflict with other team members’ work. The key to resolving problems quickly is to find them quickly; undetected conflicts become harder to solve with time. With version control in place, introduce the discipline to commit changes to the central repository frequently, multiple times a day.

 

3. Integrate new changes with an automated build

Even a centralized repository is no guarantee that new changes won’t break the existing design. Detection of conflicts is still dependent on the individual developers running the latest version of the process on their machine. Bonita BPM provides the Workspace API to automatically compile your process models. Set up an automated integration environment with a continuous integration system (like Jenkins) and the Bonita Workspace API, to monitor the version control system for changes and trigger process compilation thereby helping detect integration issues early.  

 

Read more in the best practices document.

please log in to access the asset. Login
No account yet? Create one. Sign Up