Fast Builds with Electric Cloud
Cross-Platform Software Build Acceleration
Slow software build cycles are more than just an annoyance. Whether you have long monolithic builds or a large number of smaller builds that take a long time, they are having a real impact on your development organization.
- Wasted time, frustration waiting for builds
- Fixing broken builds delays testing
- Fewer bugs fixed, fewer features added
- Developers avoid builds
- QA may skip tests to meet deadlines
A recent survey of more than 350 development professionals found that 68% reported broken builds at least a few times per month (and often weekly), and fixing those typically wasted 2 weeks per year. The majority said their builds were each more than 1 hour long, with 24% reporting builds of 2-4 hours, which translates to time not spent creating great software.
Only Electric Cloud has proven, patented technology that all but eliminates broken builds and reduces build times by as much as 20x.
Learn more about ElectricAccelerator's patented technology for software build acceleration.
For faster developer builds and build avoidance done right download SparkBuild, a free build tool compatible with GNU Make and NMake.
| Challenge |  |
|
|
Impact | |
|
|
Electric Cloud Solution |
| Long build cycles (whether long individual builds or many shorter builds per cycle) | |
|
|
Productivity comes to a halt while developers and QA wait for builds | |
|
|
The ElectricCommander build management system distributes build steps across multiple resources for parallel processing and speed improvement
The ElectricAccelerator distributed build tool accurately distributes builds at the file level for massively parallel builds and up to 20x speed improvement
|
| "Throwing hardware" at the problem is not scalable, and ultimately does not work | |
|
|
Manual approaches to parallelism share the same fatal flaw: as the level of parallelism is increased, they generate incorrect or broken builds | |
|
|
ElectricAccelerator's patented dependency management technology determines exactly which files were used to build every object file, library or executable, such that when build steps are run out of order, it automatically re-runs them in the correct order |
| Can't trust incremental builds, so developers wait to do longer, full builds | |
|
|
A full or integration build may be comprised of many additions and check-ins, so if the build breaks, teams must parse through many changes to find the cause of the breakage | |
|
|
ElectricAccelerator's eDepend feature captures complete dependency information automatically and efficiently, with no human intervention. As a result, it provides accurate and reliable incremental builds and eliminates the need for frequent full builds for small changes |
