By parallel execution of build steps and automatic change detection SBuild enables very short build times and rapid incremental builds.

Project scripts will be automatically compiled on the first run. Subsequent SBuild invocations will execute these compiled scripts almost instantly.

With a growing number of available plugins SBuild encourages standardized project setups, but without compromising flexibility. At any time, you can customize your build when needed.

SBuild does not make any assumptions about your build environment. It does not guess settings or additional buildfiles. You can always know what it will do based on one single entry point: the buildfile. Your co-workers and your CI team will thank you afterwards.

We believe, this is a requirement to achieve stable and reproducible builds over time.

SBuild integration capabilities allow tools like Ant tasks, Eclipse Aether (Maven) or Adept to integrate seamlessly.

SBuild’s plugin container is capable to isolate plugin implementations, so that plugins will not interfere with others. Each plugin has fine control which API’s it will export to it’s consumer.

SBuild is developed and published under the Apache License, Version 2.0. The source code is hosted publicly on GitHub.

You can ask questions on the mailing lists (sbuild-dev, sbuild-user), IRC, or Twitter. You can report bugs or new feature ideas on our issue tracker on GitHub. And any kind of contribution, be it pull requests, ideas, documentation or any other feedback is much appreciated.