OpenMake Meister

Continuous Integration Tab Screen

Each Workflow can be configured with its own unique Continuous Integration process.  From the Workflow Editor you will see the Continuous Integration Tab which takes you to the Continuous Integration Screen where you can define your Workflow’s unique Continuous Integration parameters.

The Continuous Integration Tab Screen displays three sections: SCM Configuration, Command, and Continuous Integration Trigger. 

SCM Configuration Section

This section allows you to define what Source Code Management Type you will use to support your Continuous Integration process. Type is the Source Code Management update command to run in order to check out the code from the SCM repository.  NOTE: The original checkout of the file from the SCM tool may be necessary if the SCM tool does not support a full checkout when performing an update action.  For example, CVS requires a cvs checkout before any cvs updates will work.  So a cvs checkout would need to be done outside of the Continuous Integration process since the Continuous Integration is just performing update or synchronize commands.

SCM Support Type

Command Section

In the Command section, you can define command settings for each highlighted Type. A unique series of Command input lines provided by each Type appear in the Command section. For example, Update from CVS for $(JOB_NAME) displays the input lines *CVS Root, CVS Options, and Update Options when you select this specific activity. Information must be provided for any input line marked with an asterisk.

Continuous Integration Trigger Section

In the Continuous Integration Trigger section, you can define when a Workflow is executed.  It can be executed, periodically on a timer.  For example, every 30 minutes or after changes to SCM repository have settled for 10 minutes.  The following fields define your Continuous Integration Trigger:

Continuous Integration Server drop-down box

Use the drop-down box to select your Continuous Integration Server.  Your Continuous Integration Server is most commonly the machine that hosts your Source Code Management (SCM) tool.   NOTE:  The only machines that are displayed in this list are those machines that have an OpenMake Remote Agent installed.   Therefore, the machine that hosts your SCM tool must have a Remote Agent installed to be displayed in this list.

CI Build Directory for check-out and monitoring on Continuous Integration Server

This directory is where the files will be updated from the SCM repository.  The SCM command defined in the Command Section will be executed in this directory to perform the update.  When executing software builds using Meister, this directory should be the same as the “Build Directory” defined in the Meister Workflow Activity using the Workflow Editor. This directory resides on the Remote Agent in which the Continuous Integration Server is running.  

File extensions to monitor for changes in the check-out directory on the on CI Server

This is a list of file extensions that should be considered when determining if a change has been made to the SCM repository.  The file extensions should be delimited by a semicolon.  For example, to monitor just changes to .c and .h files the entry field would be:  .c;.h;

Disable CI Build Trigger

The Continuous Integration is turned off for this Workflow when selected.

Execute after a Quiet Period of <x> Minutes

Continuous Integration will wait until no new files have been found for the specified number of minutes then it will execute the Workflow.  The timer is reset once a change has been found.

Execute Every

Continuous Integration will execute this workflow for the defined interval, for example, every 30 minutes.