CMake RE
powered by tipi.build & EngFlow
Remote execution for CMake
Unlock lightning-fast distributed builds with multilevel caching: Collaborate, Reuse, and Accelerate!
Explore tipi's integration with our partners at EngFlow and uncover the advantages of CMake distribution for your team. Our solution combines multilevel caching with the power of up to 10,000 cores. This not only accelerates build processes to unprecedented speeds but also trims down costs in your CI/CD minutes while minimizing developer idle time.
We've developed a CMake wrapper that allows for instant CMake builds, all while giving experts the freedom to build according to their preferences.
What's in it?
Amazing caching
Improve cache hits accross your organization by combining EngFlow's highly granular RE cache with tipi's revisioned caching technology for blazing fast incremental builds.
Distributed CMake builds
Scale your builds well beyond the limits of what a single machine can deliver with CMake Remote Execution. From hundreds to thousands of cores CMake RE can grow with your build and help you deliver faster and more reliably.
Cost control for your CI
CMake RE can help you reduce CI cost significantly by improving the usage of the machines, dynamic scaling and multilevel caching.
Serving your team hand in hand
All you know & love about tipi
Stable, clean environments on demand, tipi's source synchronization technology and tipi's first class CMake support.
tipi drives your build and is the tool you use to start the build. If your build works with tipi today, switching to the cluster powered build is a matter of seconds.
X
Awesome build cluster by EngFlow
EngFlow Remote Execution distributes builds and tests across a cluster of machines and remotely caches the results to make them faster.
Additionally get access to build analytics to better understand and tweak your build performance.
Seamless transition
A small amount of configuration and the using one of tipi's CMake RE targets is all that is required
CMake RE is designed to require little to no modification to your project to build. For project already building
with tipi the transition requires only changing the target and setting the cluster configuration.
Cluster sized to fit
The EngFlow cluster is a managed service that can be customized to your requirements in terms of size of nodes, auto-scaling requirements, expected workload and more.
The build cluster is deployed to a private cloud account and remains isolated from other users for maximum security of your code.
CMake RE builds
Distribute CMake build tasks accross the cluster
After your sources are synchronized with your tipi build node, CMake RE
distributes the individual build tasks accross the EngFlow cluster.
At all levels of the build caches are used to further increase the build speed and reeuse of build artifacts between all members of your team.
When using any of the remote build CMake RE targets, tipi
starts a build node that is located optimally to drive the build in your EngFlow cluster with minimum latency.
Talk to us at
Upcomming events:
(currently none)
Past events: