Jujutsu: a new, Git-compatible version control system [LWN.net]

Jujutsu: a new, Git-compatible version control system

Posted Jan 19, 2024 20:53 UTC (Fri) by willy (subscriber, #9762)
In reply to: Jujutsu: a new, Git-compatible version control system by bluca
Parent article: Jujutsu: a new, Git-compatible version control system

Enough months for something important to start depending on it. Then death. Followed by three forks from the last published version, all slightly incompatible. And an army of Xooglers who demand that you use the version they've determined is best.

(Is Bazel dead yet? Please please please ...)

to post comments

Jujutsu: a new, Git-compatible version control system

Posted Jan 19, 2024 22:56 UTC (Fri) by tux3 (subscriber, #101245) [Link] (3 responses)

If I followed correctly, Android AOSP had started migrating from Make to "Kati" and "Soong", and then partway through that migration they started a big migration to Bazel.

It's now a mix of everything, with Bazel as the latest and greatest, but seems a good bet that they won't be able to get rid of any of these build systems for many more years.

I can't imagine them starting _yet another_ migration to replace Bazel!

Jujutsu: a new, Git-compatible version control system

Posted Jan 20, 2024 15:41 UTC (Sat) by khim (subscriber, #9252) [Link] (2 responses)

> It's now a mix of everything, with Bazel as the latest and greatest, but seems a good bet that they won't be able to get rid of any of these build systems for many more years.

This depends on your definitions of won't be able to get rid of any of these build systems, I guess. Someone in Google realized that having three build systems is a madness, and the decision was to nix bazel… except kernel build would remain on Bazel because kernels are not built when Android is build, they are built separately and dropped into AOSP as prebuilts.

Jujutsu: a new, Git-compatible version control system

Posted Jan 20, 2024 15:53 UTC (Sat) by tux3 (subscriber, #101245) [Link]

>Someone in Google realized that having three build systems is a madness, and the decision was to nix bazel

Oh..that was not what I expected!

Then I suppose the documentation may need an update:
https://source.android.com/docs/setup/build/bazel/introdu...

>Google has a multi-year plan to migrate the Android Build system to Bazel. This migration is in early stages, but some changes can be made to current build files to start preparing them for Bazel.
>At the completion of the migration Bazel will replace all existing build systems and build configuration systems in AOSP (Make, Kati, Soong, Make-based product configuration).

Jujutsu: a new, Git-compatible version control system

Posted Jan 20, 2024 17:00 UTC (Sat) by khim (subscriber, #9252) [Link]

> Then I suppose the documentation may need an update:

I guess they still don't know what to write there. Because they still want to have bazel, in the end, just the decision was to stop using three build systems simultaneously.

So either all makefiles should be converted to soong first, or, at least, they should be convertable to bazel, at least in theory.

The actual path to that nirvana where only bazel exists is still not determined, but the path where there are three build system and none can be removed because every one of three have something unique that other two couldn't do… that was nixed.

Conversion from soong to bazel is easier than doing something to the mess that's in these remaining Makefiles thus they went back to Plan A: first convert everything from Make to Soong, then decide how to adopt bazel.

Jujutsu: a new, Git-compatible version control system

Posted Jan 22, 2024 20:48 UTC (Mon) by scottlaird (subscriber, #96306) [Link]

Bazel will never die.

Or, at least, blaze won't die, not for many years. Google depends on it for *everything* internally. It's deeply, deeply baked into a lot of infrastructure, and replacing it would probably be a decade-ish long project.