Looks quite complete. Related to that, Github recently released Actions Beta (https://github.com/features/actions), but you still need to cook your workflows.And on to the 'owning' issue, we aren't using Github Code Owners either (https://github.blog/2017-07-06-introducing-code-owners/), right? That would introduce some 'casting vote' to the PR review process, but cannot say if they need to be members of the org. Ernesto On Thu, Feb 28, 2019 at 9:45 PM Ken Dreyer <kdreyer@xxxxxxxxxx> wrote: > > Hi folks, > > From time to time we talk about improving the developer experience for > PRs and builds. > > One of the KubeVirt developers presented recently on "KubeVirt and > Prow": https://www.youtube.com/watch?v=B3nLnIk0Vc8 > > It sounds like they currently have some Jenkins infrastructure and > they are moving to Prow. This is the CI system that Google uses for > Kubernetes PRs. > > One of the things that stood out to me is the ability to delegate > merge permissions to different GitHub users for different areas of the > code tree, without having to make them members of the organization. It > can also rebase and merge once the build passes, so that could help > with the occasional build failure we see when Ceph PRs collide. > > In the past the idea of using Zuul has come up, and I wonder if Prow > could be a better choice. > > - Ken
