Post

Anybody want to come work on Tailscale's internal dev tooling/productivity, CI, bots, dashboards, etc? Pretty please? 😅

Marc-Antoine Ruel

@maruel.ca

8 Apr 2025

How has been your experience with LUCI with upstream Go?

Brad Fitzpatrick

@bradfitz.com

They switched to LUCI after I left. It seems like Go lost functionality with it honestly. I don't understand its advantages. I think it's just Chrome team staffed it and Go didn't want to staff build tools as much anymore?

8/4/25, 11:34 pm0 reposts0 likes

Marc-Antoine Ruel

@maruel.ca

8 Apr 2025

FWIU most of the DevX group went on LUCI and the Go team folks were favorable. My understanding is that it was not imposed. At the time I was there, Chrome's director for the CI wasn't happy in getting more customers for a long time. I'm curious what regressions affect you the most.

Brad Fitzpatrick

@bradfitz.com

8 Apr 2025

IIRC at least when it was first introduced we lost some OSes, builds started much slower (slower setup time), and the failures were hidden behind relatively bloated JS/CSS pages.

Marc-Antoine Ruel

@maruel.ca

9 Apr 2025

OSes is a bummer. I worked hard for the bot to work everywhere, including MIPS and I almost did s390x; I failed to convince leads was worth it. Swarming has a fairly solid cache system to improve setup for the warm case. For the cold case, it depends. HTML; I'm no web guy so I can't say. :/

Marc-Antoine Ruel

@maruel.ca

9 Apr 2025

Before leaving I tried to have teams enroll on github.com/shac-project... but I failed to get traction; another lead in another org wanted to push their server-side project and succeeded. There's a internal(sigh) long design doc that explains the trade offs.

github.comGitHub - shac-project/shac: Scalable ChecksScalable Checks. Contribute to shac-project/shac development by creating an account on GitHub.