Skip to content

Instantly share code, notes, and snippets.

@jnaulty
Last active December 6, 2019 14:24
Show Gist options
  • Save jnaulty/4e5b179d2fb7c1a8c1ba3eae16949971 to your computer and use it in GitHub Desktop.
Save jnaulty/4e5b179d2fb7c1a8c1ba3eae16949971 to your computer and use it in GitHub Desktop.
Automation and the Kubernetes Contributor Experience

Automation and the Kubernetes Contributor Experience

Aaron Crickenberger, Samsung SDS

KubeCon Europe 2018

URL: https://www.youtube.com/watch?v=BsIC7gPkH5M

[Notes on the Talk]

Solving problems in the Test Workflow

The Work

  • implementing pr workflow
  • facilitate triage workflow
  • configure and run jobs
  • provide insights into project health

Automating Analysis of Build Job Failure

Ends up in frustrating situation where you check-in build and it fails and only buildcop can solve

Prow Objectives:

  • checks conventions (coding standards)
  • make sure it builds!
  • pass unit and integration tests
  • pass e2e tests
  • perf tests (using simulation cluster with kubemark)

Code Review (PR Flow Improvements)

  • solve problem for knowing how to ask for a Review
  • critiques on CODEOWNERS file
    • assigns to all people who match that regex for that file So improve OWNERS file to look and choose selectively
  • reviewers
  • approvers
  • labels

image The project CANT live without them.

  • MERGE Commit must pass Test
  • 25% flake expected. (Test is 75% Consistent)
  • Testst N PRs at once (batch them, maintain velocity)

ISSUE TRIAGE

  • /retest command saves time by only running failed jobs

More Prow Commands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment