• FishFace@piefed.social
    link
    fedilink
    English
    arrow-up
    10
    ·
    10 hours ago

    We have a gigantic monorepo at work.

    To manage the complexity we have entire teams dedicated to aspects of it, and an insanely complex build system that makes use of remote builders and caches. A change to a single python file requires about fifteen seconds of the build system determining it needs to do no work, with all of this caching, and the cache can be invalidated unexpectedly and take twenty minutes instead. Ordinary language features in ides are routinely broken, I assume because of the difficulty of maintaining an index of that stuff on such a huge codebase. Ordinary tools like grep -R or find can only be used with care.

    • Cyberflunk@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 hours ago

      grep

      consider looking at ripgrep and semantic search tools.

      i maintain a gigantic monorepo using policies, cicd gating, pre-commit, and lots of scripting. its not unworkable, just takes process. i don’t really agree with the creators pov. but i guess i may not be a new engineer entering a team with a monolith and a bone.

      • FishFace@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 hours ago

        I don’t see how ripgrep would help with the monorepo situation. We have tooling for an equivalent of grep, but it’s based on an index, not what’s on your filesystem.