Next Webcast: How AndroidX does DevProd Engineering with Gradle Enterprise – March 31 (10:00AM – 11:00AM PDT). Learn more and register here.
Designed for Developers, Built for the Enterprise
Software scalability and availability is critical to allow organizations to handle seamlessly increased workloads and support growing amounts of data in an elastic and cost-effective manner.
Designed from Inception to Scale
From its first release, Gradle Enterprise has been designed with the explicit requirement that it scales to the largest build infrastructures on the planet. To that end, the Gradle engineering team has made extensive architectural and engineering investments to guarantee that as the platform ingests, processes, and analyzes an ever-growing amount of data, Gradle Enterprise never misses a beat.
Integrated Best-in-Class Technologies
Gradle Enterprise is designed to support your DevOps strategy leveraging the best industry-standard technologies. With great pride, Gradle has held fast to the most trustworthy architectural patterns, integrated best-in-class solutions, and curated industry-approved libraries to support its efficient and highly-available functionality. Gradle Enterprise scales with your growing organization, collecting more and more metrics, providing more and more insight, and accelerating more and more of your software development.
Adaptable to Different Build Infrastructures
Development teams vary greatly in their composition and organizational practices and Gradle Enterprise can adapt flexibly and scale to perform under very different build infrastructures. Some of our customers successfully use Gradle Enterprise to improve monorepo builds with thousands of modules and thousands of engineers. Huge monorepos, especially multi-dimensional projects such as Android apps, can produce massive amounts of data per build. While other decentralized repos accelerate hundreds of thousands of different projects and millions of local and CI builds per day, while producing significantly less data and being more complex and error-prone. In either scenario, we’ve taken the right steps to assure that Gradle Enterprise performs consistently and reliably no matter which patterns development teams adopt.
Aetna completely agrees that Gradle Enterprise is a mission-critical component of their developer productivity strategy, scales well, and will meet the service-level expectations of any enterprisewide deployment.
Flexible Installation Options
Install Gradle Enterprise to a single-host as a shrink wrapped appliance, or to a Kubernetes cluster for more sophisticated deployments.
HA and Scalability for all non-DB-related Services
Gradle Enterprise’s native support for Kubernetes allows for seamless elastic scaling and high availability. Horizontal scaling can be enabled as part of Gradle Enterprise’s streamlined built-in configuration, allowing full control over the number of replicas deployed to support loads by using native orchestration functionality.
User-Managed DB Option
Gradle Enterprise supports a user-managed Postgres compatible RDBMS for both single-host appliance installations and Kubernetes-based installations. PostgreSQL’s highly reliable system adds to our repertoire of thoughtfully curated components. Leveraging Postgres cloud offerings such as Amazon RDS and Aurora can make installation administration more convenient, provides HA for the DB, improves performance, and simplifies backups.
Test Distribution Elasticity
REST APIs allow auto-scaling Test Distribution agents for any compute platform, increasing throughput and minimizing costs.
Distributed Remote Cache Nodes
Native/distributed architecture allows build cache nodes to replicate and scale to any team and SDLC solution. This redundancy improves throughput for distributed teams and improves uptime.
Integration with Monitoring Solutions
An Export API and RESTful monitoring endpoints allows the solution to be managed and observed by popular third-party tools, such as Prometheus and Grafana.
Configurable Retention Policies
Data held in the platform for build caching and Build Scans can be configured for retention based on occupied storage, age, or both. Automated storage management and proactive alerting mechanisms ensure that the platform remains available across any substrate.
Raw build data is consumed and acknowledged by the backend service immediately so that even under high load you will not lose any data.
For any given project, datasets don’t change significantly across multiple builds. By analysing and segregating data that tends to change versus data that doesn’t, the size of data sets per build can be minimized.
Post-optimization, any data sent across the wire to the backend service is compressed before uploading, reducing the overall amount of bandwidth needed and latency in processing.
Easy to operate performance
Gradle Enterprise uses sophisticated caching and preemptive computation techniques to make querying build data fast, without the need for specialized and complicated data processing infrastructure.
Build Scan data is intelligently queued for processing and analysis. Active users who are currently debugging builds will be automatically prioritized, leading to a smoother user experience and better overall perceived availability.
More Gradle Enterprise Industrial-Strength Proof Points
|Enterprises rate Gradle Enterprise Scalability 4.95/5.00 on Gartner Peer Insights|
|The leading DevProd-focused companies as well as 10 of the top 30 U.S. companies have successfully deployed Gradle Enterprise at the massive scale necessary to support their dedicated teams.|
|LinkedIn uses Gradle Enterprise at massive scale, supporting over 300,000 daily builds of their application code! Read their story.|