Trying out a new CI system

[Heschi Kreinick]

Hello, gophers!

A while ago, the release team started evaluating replacements for our current CI system. After some research we decided that LUCI, the Chrome project's CI system, is the strongest candidate. For the past couple of months, we've been setting up a prototype project, which is now ready for wider experimentation. This week we're opening it up to members of the Go team to trigger, so you may start seeing comments from "Go LUCI" and "triciu...@appspot.com" on CLs.

LUCI is a large, mature project that already has a lot of features that we've wanted to build for a long time and never been able to. As an example, the presubmit UX is much better: it's integrated with the Gerrit Checks UI, supports structured test output so you don't have to scroll through a text log to find test failures, and has a UI for its version of SlowBots. We think it'll be a significant improvement over the current system.

We have a little bit of work left to do to set up the ACLs for non-Googlers. I'm hoping we'll be ready for all of you to try it out in the next couple of weeks. We're looking forward to your feedback once we are. After everyone's had a chance to try it out, we'll make our final decision about whether to move forward.

Thanks,

Heschi for the Go Release Team

[Heschi Kreinick]

We've finished setting up the ACLs. Everyone can now see build results, and those of you with TryBot access can vote a new label, Commit-Queue +1, to trigger a LUCI presubmit run.

As a reminder, this is still just a trial -- it hasn't replaced the existing TryBot infrastructure. You still need to run TryBots on your CLs to get full results.

Some things to check out:

• Nice UI for which builds are running, passed, and failed; see the red chips on my test CL.
• Integrated static analysis, including suggested fixes. We only have a couple of analyses set up so far, but we have lots of ideas for more.
• Structured test results -- no more searching text logs to find the failing test.
• Build dashboards that may eventually replace build.golang.org.
• UI for picking additional builders -- click "Choose tryjobs" on a CL.

If you have any feedback or comments, feel free to comment here or file an issue.

Thanks,

Heschi for the Go Release Team

[Meng Zhuo]

Hi, Heschi

I try to start a LUCI check but it says  "CV cannot start a Run for mzh because the user is neither the CL owner nor a committer."

Here is the CL https://go-review.googlesource.com/c/go/+/481575

What shoud I do? Thanks?

[Heschi Kreinick]

Thanks for the report. This appears to be working as intended for LUCI, but I can see how it's a problem. We'll raise it with them. In the meantime, you can run it on your own CLs to give it a try.

--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-dev/81454e39-2e22-44a5-a067-a760297d33ccn%40googlegroups.com.

[Heschi Kreinick]

Reported to the LUCI team as https://crbug.com/1443582.

[Meng Zhuo]

Thanks!

[Heschi Kreinick]

There hasn't been much feedback, which I interpret to mean that nobody sees major problems. With that, we will move forward with our migration.

We will need help from builder maintainers as the migration continues. I'll start a new thread next week about that.

Thanks,

Heschi for the Go Release Team