Compass Version1.1

TOC

Build Configurations

The Build Configurations section on the administration page allows administrators to manage what build configurations are available for build plans and Compass Build Clients.

A Build Configuration is Compass name for each Operating System/Machine/Configuration that a build plan could be executed on. In most installations, there is one build configuration for each operating system that the source code is to built on. Occasionally the same OS may be used but with different versions of a compiler (i.e. gcc3.1 and gcc3.2). Or the environment of a machine may dictate how code is built or executed and different machine configurations require different Compass Build Clients despite the same OS and Compiler.

Because of these situations, compass allows administrators to set up any number of build configurations named anything that is appropriate. On the administration page, the following section lets administrators add and remove build configurations:

As you can see from the above image, there the Build Configurations section contains a list of existing configurations and buttons to delete and add new configurations. Care must be taken when both adding and removing build configurations.

When adding new configurations, it is important to go through every build plan and make sure that they appropriate build plans all use the new configuration.

When deleting configurations, all build plans that use that build configuration will stop using it. It is important to make sure that a build plan is not relying on a deleted configuration to execute builds.

Finally, whenever a configuration is added or deleted, Administrators will need to update any affected Compass Build Clients by modifying the Build Client's config file. The Config file for each Compas Build Client specifies which build configuration the client is building for. when a Build Client tries to connect with the Compass Server, if the build Configuration is not valid, an error is reported in the Build Client's log.