Set up continuous integration

On your Subversion server, create a shared project that can be accessed by the business analysts and developers working on processes and by the CI tools. After you have create your shared project you may develop your processes in this project and/or import existing processes. Each Bonita Studio user must connect to the repository.

Define an environment for configuring processes for CI. This environment will be stored in the shared project together with your process definitions.

Prepare Bonita Studio on the CI server: Bonita Studio includes a BonitaStudioBuilder script to build processes in a CI environment. Install Bonita Studio as follows:

Create Jenkins job: In Jenkins, create a new job of type "Build a free-style software project". Specify a job name for example "Bonita-BuildProcesses".

Configure Jenkins job:

Run the Jenkins job
Run the "Bonita-BuildProcesses" Jenkins job. When it is finished, the Maven artifact com.acme.bonita:process-bars:1.0.0-SNAPSHOT in installed in the local Maven repository of the CI server. The generated processes package is also available as a job build artifact in Jenkins.

In your IDE create a new Maven project and share it (for example using SVN or Git).

Configure local access to Bonita Engine.

As we want to test processes build with a Bonita Subscription edition, you need to configure the required Maven artifacts. You should also check that there is a valid license file in ${bonita.client.home}/ and the System property bonita.client.home set to this folder path.

We recommend that you write your test cases in the src/test/java folder of your project and put all related resources (Bar files, organization file…​) in src/test/resources.

Before installing your processes load the relevant organization (regarding your actor mapping). You may have to export your organization from a Bonita Studio: Menu Organization > Export, Select your Organization.

private void installOrganization() {
    File organizationFile = new File(MyTestCase.class.getResource("/ACME.xml").getFile())
    String organizationContent = getFileContent(organizationFile)
    getIdentityAPI().importOrganization(organizationContent)
}

Then as a basic test, we try to deploy each generated processes. For example:

@Test
void deploy() throws Exception {
    // Retrieve automatically generated bars as a Map<filename, fileContent>
    Map<String, InputStream> bars = getBars()
    Assert.assertTrue("No bar found in resources", !bars.isEmpty())

    // For each bar deploy and enable it
    for(Entry<String, InputStream> entry : bars.entrySet()) {
        BusinessArchive archive = BusinessArchiveFactory.readBusinessArchive(entry.getValue())
        final String entryKey = entry.getKey()
        ProcessDefinition definition = getProcessAPI().deploy(archive)
        final long defId = definition.getId()
        Assert.assertNotNull("Failed to deploy "+entryKey, definition)
        getProcessAPI().enableProcess(defId)
        getProcessAPI().disableProcess(defId)
        getProcessAPI().deleteProcessDefinition(defId)
    }
}

Create a new freestyle job in Jenkins

Configure the source code management to retrieve your Maven project.

Add a build step

Select "Invoke top-level Maven targets"

Use following Goal: org.apache.maven.plugins:maven-dependency-plugin:2.7:get

In properties, set the following:

Then add another build step to unzip the artifact. Select "Execute shell", and use the command unzip process-bars-1.0.0-SNAPSHOT.zip -d project/src/test/resources.

Finally, add another Maven 3 build step to build the test project: