Sender: golang-dev@googlegroups.com
Received-SPF: pass (google.com: domain of ori@eigenstate.org designates 206.124.132.107 as permitted sender) client-ip=206.124.132.107;
To: heschi@google.com, ori@eigenstate.org
CC: golang-dev@googlegroups.com
Subject: Re: [golang-dev] 9front-amd64 builder?
Date: Wed, 25 Jan 2023 21:19:32 -0500
From: ori@eigenstate.org
Mailing-list: list golang-dev@googlegroups.com; contact golang-dev+owners@googlegroups.com

Quoth 'Heschi Kreinick' via golang-dev <golang-dev@googlegroups.com>:
> Yeah, a GCP builder is preferred. Historically, you would provide a script
> in https://cs.opensource.google/go/x/build/+/master:env/ to build the
> image, and someone from the Go team with permissions to create the image
> would run it. Then you'd send a CL to
> https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go
> adding a host type and builder using that image. That's still an option.
> 
> However, that creates a maintenance burden on the Go team, and
> https://go.dev/issue/53383 reflects our desire to empower port maintainers
> to take responsibility for their own ports. I think it would be good if
> port maintainers controlled their own builder images, but that requires us
> to figure out security and process concerns. I'm not sure when we'll make
> that possible.
> 
> So: if this is very important for some reason, you can send us CLs and
> we'll build the image when we get a chance. Otherwise, please check back in
> a few months and maybe we'll have improved the processes.

it's been a few months; pinging this·

-- 
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-dev/89FDAD59497DA2AF9E4236AB44ABF13A%40eigenstate.org.