Pants is a scalable software build system. It is useful for code repositories of all sizes, but is particularly valuable for those containing multiple distinct but interdependent pieces.
Pants orchestrates the various tools and steps that process your source code into deployable software, including:
- Dependency resolution
- Code generation
- Compilation/type checking
- Project introspection
Pants is in a similar category as tools such as
bazel and others. Its design leans on ideas and inspiration from these earlier tools, while optimizing for speed, correctness, and ergonomics in today's real-world use cases.
Pants is useful for repos of all sizes, but is particularly valuable for those containing multiple distinct but interdependent pieces.
Pants allows you to have a monorepo: a codebase containing multiple projects—often using multiple programming languages and frameworks—in a single unified repository. If you want to scale your codebase without breaking it up into multiple disconnected repos, with all the versioning and maintenance headaches that causes, Pants provides the tooling for you to do so effectively.
Pants is designed for fast, consistent builds. Some noteworthy features include:
- Dependency modeling with minimal boilerplate.
- Fine-grained invalidation.
- Shared result caching.
- Concurrent execution.
- Remote execution.
- Unified interface for multiple tools and languages.
- Extensibility and customizability via a plugin API.
Pants ships with support for Python, Shell, Docker, and Go. Support for other languages, including Java, Scala, and more is coming soon.
See here for details about the Pants engine.
Pants is making engineering teams productive and happy at a range of companies and organizations. See a sample of them here!
Pants 1 vs. 2
This documentation is for Pants 2, which is a ground-up redesign of Pants based on lessons from the past 10 years of development. See here for Pants v1 documentation.
Updated almost 2 years ago