Multi-Platform Build Scenario

Marie is a build master on a multi-platform software project. The development team has to deliver a Windows version as well as a Linux version of the software product. This will require two different sets of binaries possibly produced by two different build scripts.

Marie can use AnthillPro3 to define an appropriate multi-platform build process. She can configure AnthillPro3 to execute one build that will produce a set of artifacts for each of the target platforms. Marie would define some steps that are common to the build; for example creating a unique build identifier, applying a label to the source code repository, and possibly retrieving the source code to be used for the build. Then, Marie can define the process that should be performed on each target platform. For example, when performing the build on Windows, certain environment variables may need to be set prior to executing Windows specific build scripts. And on Linux, different environment variables may need to be set and a different build script may need to be invoked. Marie can define a different set of steps to be executed by AnthillPro3 during the build for each target platform, or Marie can define a single set of steps that is to be executed on each target platform. In the latter case, the platform specific differences would be handled by dynamic properties managed by AnthillPro3.

Marie can define Agent Filters that will be used to select the machines on which each platform specific portion of the builds will take place. Marie can either select the exact machine (agent) or she can define a selector that will select the most appropriate agent at run-time based on the load on the agent as well as agent specific properties such as the agent platform, number of CPUs, CPU type, system memory, availability of environmental dependencies such as compiler versions, and more.

In the end, Marie saved tons of time, her error level approached zero, and she got the corner office.