If you're part of a software development team that performs multiple daily builds, then you might replace the term "continuous integration" with "continuous build failure." A company called Electric Cloud may offer a solution. The software production tools maker later this month will begin shipping ElectricCommander 3.0, the latest version of its build automation system that can now check or "preflight" newly modified source code to determine if it will correctly build into an application. Version 3.0 also now integrates with Eclipse and Visual Studio.

ElectricCommander automates the process of assembling components that make up a software program and "building" them into a running application. It's independent of development language (C/C++, Java, .NET, etc.) and build utility (Ant, Maven, Make, etc.), and supports numerous scripting languages, including perl, Python, bash and Tcl. It also works with software configuration management systems AccuRev, ClearCase, Perforce, Subversion and Synergy, if you have one.

"The preflight build and test functionality enables developers to run builds and tests on production hardware before checking in code to the SCM system, thereby catching errors before they impact the productivity of the rest of the team," said Electric Cloud CEO Mike Maciag. The tool helps eliminate the problem of a successful build on one machine and a failure on another due to differences in machine type and configuration, tool versions or platform.

The tool works by applying an overlay of developer changes through production build and test procedures across all targets, giving developers the chance to commit only if their changes worked. "Automated preflight and tests put the power to compile and test each change before check-in," according to a company document. This early feedback about the potential failure of a build helps enable continuous successful integration.

If you want to see a live demo and happen to be at the Austin Game Developers Conference in Austin, Texas, today (the final day) between 10:00 am and 3:00 pm local time, stop at booth 431. The company did not disclose pricing or an exact availability date.

Dani AI

Generated

As introduced the preflight concept, here is a compact, practical playbook for making preflight builds effective rather than intrusive.

A simple, reliable workflow:

  • Run lightweight checks locally first (syntax, linters, fast unit tests) to avoid obvious failures.
  • Produce a patch or shelved change and apply it to a clean CI workspace (no local caches or IDE state). The CI agent runs the same build and smoke tests that protect the mainline.
  • If smoke checks pass, run the longer integration and environment-sensitive tests; only then allow the change to be merged (gated merge or merge-on-success).
  • Fail fast and return clear failure logs so the change author can act immediately.

Quick commands (examples only; adapt to the project toolchain):

# Perl: syntax check and run test directory
perl -c lib/My/Module.pm
prove -l t/
# Visual Studio/MSBuild: clean parallel build
msbuild MySolution.sln /m /p:Configuration=Release

Troubleshooting and operational tips:

  • If a change builds locally but fails on CI, compare tool versions, PATH, environment variables and native deps; reproduce CI with a container or VM snapshot.
  • Keep preflight fast by splitting checks (fast local + CI smoke + extended CI) and by running only affected tests where possible.
  • Preserve developer flow: make failures actionable, surface useful logs, and expand preflight coverage incrementally (start with compile+smoke tests, then add integration suites).
  • Use artifact caches, incremental builds, and pinned toolchains on CI agents to reduce noise and improve repeatability.

This approach turns preflight from a marketing phrase into a practical guardrail that keeps the trunk healthy without creating a bottleneck.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.