Proposal: Migrate Build Automation to k8s prow.

[jeremyje]

Proposal Document: https://docs.google.com/document/d/1BOhIKP3N9TjOEUSn28jZvLSTFWrE7DKg66LANNerLdg
Open Match Issue: googleforgames/open-match#107

[markmandel]

What sort of things do we need? Prow seems very complicated.

[jeremyje]

The plan is to use the k8s prow so we are not managing the instance. We mainly need to provide the config.yaml and plugins.yaml files.

In the Agones case it seems like it'll remove the need to have agones-bot.

[markmandel]

Was thinking about this today - would it be useful to have a list of all the custom CI/build pipeline things that currently exist?

[roberthbailey]

Yes, having a list would be very helpful.

[roberthbailey]

@Kuqd - I saw your (old) note in Slack about cloud build e2e vs. prow and thought we should re-open the discussion. I think it'd be a great topic for the community meeting scheduled on the 25th. Could you take another pass over the document before then and add some comments?

[roberthbailey]

@heartrobotninja - did you have any other comments you wanted to leave on the doc? As I mentioned in the above comment, I think this would be a great topic to discuss at the next community meeting (on the 25th of this month).

[cyriltovena]

Will do ! Thank you

[roberthbailey]

This topic was discussed at the community meeting today (notes) and the consensus is that we should move to prow.

Since not everyone who wants to give input may have had a chance to attend the meeting, we are going to initiate a lazy consensus process: we will start moving to prow unless anyone raises objections before May 1st (next Wednesday).

[roberthbailey]

/assign

[markmandel]

@roberthbailey do we still want to migrate? Seems like Cloud Build is still fine?

If anything, we could move the things we use prow for to Github Actions, and remove some of the noise in our PRs.

[roberthbailey]

Cloud Build has definitely been working for what we need. At this point I'm not seeing a strong reason to change things around.

I don't know enough about Github Actions to know whether that would be an improvement, but if so we should open a separate issue to track it.

I'm going to close this issue as obsolete.