gcp-gradle-build-cache

By androidx

Gcp-gradle-build-cache Alternatives

Similar projects and alternatives to gcp-gradle-build-cache

  • nx

    Smart Monorepos · Fast CI

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better gcp-gradle-build-cache alternative or higher similarity.

gcp-gradle-build-cache reviews and mentions

Posts with mentions or reviews of gcp-gradle-build-cache. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-09.
  • Any teams out there using Gradle enterprise cache?
    1 project | /r/androiddev | 10 Dec 2022
    https://github.com/androidx/gcp-gradle-build-cache take a stab at this, it was my plan of attack before I quit my job out of frustration
  • Experiment: The costs of slow build times
    2 projects | news.ycombinator.com | 9 Dec 2022
    Most people's CI issues can be solved in three easy steps.

    1/ Get an actual, real machine. We run all of our CI for 10 devs out of a single 13900K / 64GB RAM machine, from a Jenkins setup that I've done over a weekend that has a single runner. 5-10 minute runs for PR validations (500kloc app, shitloads of tests, etc), 3 minutes for app builds. Buy it and host it yourself, or rent from Hetzner. You don't need a sysadmin for that. Machine is fucked ? Just restart it lol. Dependencies out of date ? Just upgrade your dockerfile, or your ansible setup and reinstall it all.

    2/ Cache. Cache. Cache. Cache. Cache. It isn't hard if you're not looking for perfect. Nobody cares if sometimes, randomly you have one small module that rebuilds even though it shouldn't have: the beefy machine is here to make sure it takes 10 seconds anyways. All that matters is that you never have a cache that says even though it shouldn't. And to solve this: don't make the cache yourself. Your build tool either has it (Gradle, Maven, Webpack, etc), or there's a widely used tool that works (ccache, etc.). How do you store your cache ? Not on the build machine. Because that fucking sucks. Make it a remote cache (If using gradle, you can pay for enterprise if you're feeling optimistic, host a gradle remote cache yourself, or use https://github.com/androidx/gcp-gradle-build-cache and forget about it. The running costs of it have been well under a hundred dollars over a year).

    3/ Less important, but know your build tool. I've spent a lot of time rewriting Gradle projects to avoid cross configuration, allow configuration caching, allow parallel configuration, etc. The same applies to everything else. Your build tool should be part of your knowledge.

  • Slow UI tests on pipeline
    1 project | /r/androiddev | 8 Aug 2022
    On the last, not too hard if you have modularised https://github.com/androidx/gcp-gradle-build-cache
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 1 May 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic gcp-gradle-build-cache repo stats
3
128
7.5
7 days ago

androidx/gcp-gradle-build-cache is an open source project licensed under Apache License 2.0 which is an OSI approved license.

The primary programming language of gcp-gradle-build-cache is Kotlin.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com