Begin productive work immediately at the start of each day:

You can clone a known-good, prebuilt, pre-tested tree in seconds and start editing.

You don’t need to wait to download all the latest source code from the repository — only the files you actually need are downloaded, and only as you need them.

You don’t need to wait for a build to complete — all of the build results are already available to you under your newly cloned Cascade tree’s “results” directory.

No “flaky” builds or “make clean”-style voodoo magic. Cascade already ran the build for you, and it ran it in a fresh, clean, deterministic sandbox.

You can be confident that you are starting from a tree that works, because Cascade will automatically select the last-known-good revision based on its regression testing.

Speed up development cycles and improve software quality:

Find who broke a build

The less time you spend waiting for builds and tests and fighting other people’s broken code, the more time you can spend on other work.

By setting up automated regression tests, you can enforce a minimum software quality bar, and keep raising that bar over time. Since the cost of fixing a bug increases the longer it stays in your codebase, the higher quality your work today, the less time and money you’ll need to spend on bug fixing later down the road.

If a break does slip through, you’ll know exactly which change it was, rather than having to guess or binary search to figure out which one of 20 possible candidate changes caused the problem.

No need to “cut builds” for QA. Just pick a revision number that’s passed your regressions, and QA can immediately start checking things out.

Automate your entire build and release flow — just set things up so that a final, ready-to-release installer binary or CD image pops out of Cascade. Once you’ve done this, Cascade will start regression-testing your release flow. You won’t have to manually cut releases any more, or worry about what happens if your build/release engineer is out for a day.

Checkpoint your work without having to commit it to the repository:

Checkpoint a change

Don’t worry about losing your work in a disk crash or due to human error — just checkpoint your changes on a regular basis.

Unlike real commits to the repository, checkpoints are lightweight. You don’t need to worry about doing “too many” checkpoints and eventually filling up the server with useless data. Administrators can easily purge old checkpoints (e.g., those older than a month).

Efficiently hand off work between engineers or transfer changes between PCs, without having to manually email around files.

Cascade can run the tasks affected by your change in advance and tell you what builds/tests, if any, your change would break were you to commit it. No longer do you need to commit and “hope for the best” on all those platforms you didn’t have time to test!

Accelerate multi-platform development:

Know what platforms will break before, not after, you commit

Set up builds/regression tests for all your target platforms in the Cascade cluster, so that you know right away if anyone breaks a particular target platform.

With Cascade, you don’t need to have an operating system installed on a local PC in order to be able to build for it — you just need to have an instance of it in your cluster. Windows developers can ask Cascade to do Linux and Mac builds on their behalf, for example. If everyone checkpoints their changes and has Cascade test them on all platforms before committing, you can catch these breaks ahead of time, greatly reducing the frequency of build and test breaks.

If you do need to test your changes locally on multiple platforms, Cascade’s checkpointing/cloning functionality can help you move your changes back and forth between PCs more easily.

Build on your existing investment:

You’ve probably invested a lot of time and energy into your current repository, tools, and scripts.

Cascade allows you to build on that investment instead of forcing you to throw it away.

You can start small, with just a few people using Cascade, and gradually roll it out over time at whatever pace you find comfortable.

Have as many trees as you want:

In Cascade, you can clone as many trees as you want. Unlike traditional revision control systems, creating more trees is cheap — it takes just seconds and consumes almost no storage.

If you need to shelve a project temporarily and work on something else, you don’t need to worry about whether your two sets of changes will collide — just create a brand new tree.

If you corrupted or deleted a bunch of files in your tree by accident (say, by making a typo in a command), you don’t need to try to fix your mistake — just create a brand new tree.

Free Trial, No Risk:

Cascade is completely free for personal use, even in a corporate environment.