The Hyper-Automated Pipeline, or Why the Matrix Must Win
summary
Describes building a hyper-automated CI/CD pipeline for JavaScript and TypeScript projects to prevent human errors like accidental pushes to master, inconsistent formatting (tabs vs spaces), and missing changelogs. Explains using automated tooling and enforcement in the repo to take control of quality and developer workflow while keeping developers productive and happy.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:13Why Matrix must win
- 3:01Good vs evil
- 5:28Human vs machine
- 8:40Hyper-automated pipeline
- 10:06Feedback speed and cleanliness
- 13:55Types and instant feedback
- 15:23Real-time tests and validation
- 16:45Unified code style
- 18:36Automate where it makes sense
- 20:25Project settings automation
- 24:42Standard run commands
- 25:26IDE templates and settings
- 27:36Jira task autocompletion
- 29:25Forcing best practices
- 30:29Linting everything
- 31:32Duplicate code detection
- 32:39Commit and changelog linting
- 34:23Lighthouse accessibility
- 36:12Bots and automated checks
- 37:37Automate everything
- 38:45OpenAPI client generation
- 41:16Swagger API generation
- 42:19Feature toggles automation
- 43:24JHipster generation
- 45:11When automation harms
- 46:16Manstein matrix hard work
- 47:21Q&A
- 49:05Legacy project automation
- 54:45Q&A
related talks
15mAutomate It: A Hyperautomated Pipeline
41mThe Pipeline-Driven Organization
50mWhy You Need a Software Delivery Machine
44mThe Pipeline Driven Organization｜
46mHow to Automate and Not Go Crazy?
21mBuild your JS Pipeline in Incremental Fashion
55mContinuous Deployment Workflows for Modern JavaScript
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers