![]() |
OpenMake Meister |
Continuous Integration is a Workflow automation process that can be “triggered” upon a particular external action, most commonly a source code check-in. The machine that triggers the Continuous Integration Workflow is referred to as the Continuous Integration Server. If you are using the free version of Meister, it can be upgraded to support distributed builds and Remote Agent that manages the Continuous Integration process across multiple machines with Server Pooling.
Each Continuous Integration Workflow can be configured with its own unique Continuous Integration process using the Workflow Editor Continuous Integration Tab. Once you have defined your Workflow you can configure your Workflow’s Continuous Integration parameters that controls how frequently your Continuous Integration Workflow loop will execute.
More:
Setup of the Continuous Integration Server Remote Agents
Defining Workflows for Local Continuous Integration
Defining Workflows for Team Continuous Integration
Configuring your Continuous Integration
Improving Continuous Integration using Build Avoidance
Improving CI with Continuous Build Scripts
Steps in a Pre-commit Workflow
Setting up a Pre-commit Workflow in Meister
Defining Dependency Directories to Support Pre-commit Builds
Executing Pre-commit Builds Outside of Your IDE