Bazel vs Buck vs Pants
Overview
Share your Stack
Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.
CLI (Node.js)
Manual
Detailed Comparison
Pants is a build system for Java, Scala and Python. It works particularly well for a source code repository that contains many distinct projects. | Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment. | Buck encourages the creation of small, reusable modules consisting of code and resources, and supports a variety of languages on many platforms. |
Builds Java, Scala, and Python.;Adding support for new languages is straightforward.;Supports code generation: thrift, protocol buffers, custom code generators.;Resolves external JVM and Python dependencies.;Runs tests.;Spawns Python and Scala REPLs with appropriate load paths.;Creates deployable packages.;Scales to large repos with many interdependent modules.;Designed for incremental builds.;Support for local and distributed caching.;Especially fast for Scala builds, compared to alternatives.;Builds standalone python executables (PEX files);Has a plugin system to add custom features and override stock behavior.;Runs on Linux and Mac OS X. | Multi-language support: Bazel supports Java, Objective-C and C++ out of the box, and can be extended to support arbitrary programming languages;High-level build language: Projects are described in the BUILD language, a concise text format that describes a project as sets of small interconnected libraries, binaries and tests. By contrast, with tools like Make you have to describe individual files and compiler invocations;Multi-platform support: The same tool and the same BUILD files can be used to build software for different architectures, and even different platforms. At Google, we use Bazel to build both server applications running on systems in our data centers and client apps running on mobile phones;Reproducibility: In BUILD files, each library, test, and binary must specify its direct dependencies completely. Bazel uses this dependency information to know what must be rebuilt when you make changes to a source file, and which tasks can run in parallel. This means that all builds are incremental and will always produce the same result;Scalable: Bazel can handle large builds | Speed up your Android builds. Buck builds independent artifacts in parallel to take advantage of multiple cores. Further, it reduces incremental build times by keeping track of unchanged modules so that the minimal set of modules is rebuilt.;Introduce ad-hoc build steps for building artifacts that are not supported out-of-the-box using the standard Ant build scripts for Android.;Keep the logic for generating build rules in the build system instead of requiring a separate system to generate build files.;Generate code-coverage metrics for your unit tests.;Generate an IntelliJ project based on your build rules. This makes Buck ideal for both local development builds in an IDE as well as headless builds on a continuous integration machine.;Make sense of your build dependencie |
Statistics | ||
GitHub Stars 3.7K | GitHub Stars - | GitHub Stars 8.6K |
GitHub Forks 674 | GitHub Forks - | GitHub Forks 1.1K |
Stacks 23 | Stacks 314 | Stacks 27 |
Followers 86 | Followers 579 | Followers 145 |
Votes 30 | Votes 133 | Votes 8 |
Pros & Cons | ||
Pros
| Pros
Cons
| Pros
Cons
|
Integrations | ||
| No integrations available | ||
What are some alternatives to Pants, Bazel, Buck?
Apache Maven
Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
Gradle
Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites.
JitPack
JitPack is an easy to use package repository for Gradle/Sbt and Maven projects. We build GitHub projects on demand and provides ready-to-use packages.
SBT
It is similar to Java's Maven and Ant. Its main features are: Native support for compiling Scala code and integrating with many Scala test frameworks.
Apache Ant
Ant is a Java-based build tool. In theory, it is kind of like Make, without Make's wrinkles and with the full portability of pure Java code.
Please
Please is a cross-language build system with an emphasis on high performance, extensibility and reproduceability. It supports a number of popular languages and can automate nearly any aspect of your build process.
CMake
It is used to control the software compilation process using simple platform and compiler independent configuration files, and generate native makefiles and workspaces that can be used in the compiler environment of the user's choice.
Sonatype Nexus
It is an open source repository that supports many artifact formats, including Docker, Java™ and npm. With the Nexus tool integration, pipelines in your toolchain can publish and retrieve versioned apps and their dependencies
JFrog Artifactory
It integrates with your existing ecosystem supporting end-to-end binary management that overcomes the complexity of working with different software package management systems, and provides consistency to your CI/CD workflow.
EventBus
It enables central communication to decoupled classes with just a few lines of code – simplifying the code, removing dependencies, and speeding up app development.
