Continuous integration examples

Jenkins

The Jenkins continuous integration server contains a maven project plugin that can easily be configured to build, test and deploy projects with the event processing maven plugin.

Project type

When creating a job, use the Maven project type :

Jenkins new project

Set environment

The environment variable TIBCO_EP_HOME must be defined - setting it to the jenkins workspace is recommended :

Jenkins environment

Build step

The maven goal has to be defined - typically this will be deploy so that the full default lifecycle is executed. Its also recommended to use a maven repository private to the workspace :

Jenkins build

It is recommended to pass the environment variable BUILD_ID to created processes so that jenkins can find and kill any left over processes :

$ mvn -DenvironmentVariables=BUILD_ID=${BUILD_ID} ...

Other configurations

  1. The source code management has to be defined so that Jenkins can find the source.

  2. Suitable build nodes have to be defined

  3. Additional Maven goals such as site and sonar can be defined.

  4. Email notifications to the development team

  5. Centralized Maven settings