Skip to content

Latest commit

 

History

History
47 lines (31 loc) · 1.86 KB

0008-cache-js-toolchain-build-results.md

File metadata and controls

47 lines (31 loc) · 1.86 KB
Raw

Caching of the build results of the JS toolchain

  • Status: accepted
  • Deciders: Thomas GERBET
  • Date: 2022-04-01 (experimentation started on 2021-12-31)

Technical Story: request #24241

Context and Problem Statement

Tuleap is (mostly) a monorepo and building it consume a non-negligible amount of time and resources. This is an annoyance for developers because each time they pull sources they might need to rebuild the integrality of Tuleap even if only a small part has changed.

As Tuleap grows bigger and new tools are introduced (e.g. converting some existing code to TypeScript to typecheck it) the issue becomes more visible. Having the possibility to do incremental builds would lead to a better developer experience.

Considered Options

Decision Outcome

After some testing and refactoring of the code base, Turborepo appears to be a good solution for a first introduction to this space. It is easy to apprehend and do not force us to learn from scratch something more complex. If necessary it will still be possible to evolve to something else as Turborepo does not hook into the build tools.

Pros and Cons of the Options

Use Nx

  • Good, because it is a well established player in this space (we are less likely to hit bugs when using base features)
  • Bad, because it does not seem easy to introduce progressively
  • Bad, because it has a steep learning curve

Use Turborepo

  • Good, because setup is easy
  • Good, because we can progressively introduce it
  • Bad, because it is a quite recent project so we might encounter some infancy issues along the way

Use Bazel

  • Bad, it has a very steep learning curve