- Accelerate process execution and diminish wait times for practically any concurrent, time-consuming execution which requires a CPU, such as compiling code, assets creation, continuous delivery builds and more
- Implementing Incredibuild is instantaneous, requires no changes to source code, no additional hardware,and no change to your current set-up.
- Incredibuild’s build visualization tool has many advantages for tracking historical executions, easily detecting errors and bottlenecks and much more.
- Easy integration with existing code and scripts - Incredibuild does not no require you to make any changes to existing source code or build scripts. All you need to do is adding the Incredibuild command (ib_console) before your original build command, and instructing your tool (whether a build tool, test script, or any other tool) to run a large number of tasks in parallel.For example, when using xcodebuild, enter a high value for the -jobs flag, and run your build.
- Usage of different build tools and applications in one distribution Environment - Incredibuild can be used in a heterogeneous environment of build tools and applications.
- Easy incorporation of additional commercial or homegrown build tools - Incredibuild is a generic all-inclusive platform. By default, Incredibuild provides support for many common build tools.
- Execution of multiple builds simultaneously on the same machine - Incredibuild allows two or more developers to build on the same machine at the same time. For example, on a machine with 16 cores, 4 builds can be run simultaneously, while each build uses 4 cores.
-
Easy generation of predefined and customized Reports - Incredibuild provides you with a Report module, which analyzes the execution of builds and allows you to gain valuable information, such as:
- Detect anomalies during continuous integration, by comparing a known stable build with a continuous or nightly build.
-
Query Incredibuild database as part of your CI scripts, to automatically discover “red flags”, like:
- Some tasks are taking longer than expected.
- Too many tasks are being executed.
- StdErr is different than a benchmark build.