Remove your Testing Bottleneck with CI/CD Pipelines
summary
Shows a concrete CI/CD walkthrough: a multi‑tier app pushed by GitHub webhook or polling into a Jenkins pipeline that runs linting, unit tests, static security scans, black‑box and integration suites, and then deploys to a dormant node for canary deployments or blue/green cutovers. Covers branch strategies (GitHub Flow vs long‑lived branches), JIRA stage‑gate automation using labels, how to keep regression suites fast, and when feature toggles or rollbacks are actually used.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:33Testers and DevOps
- 7:01DevOps for testing
- 9:06CI/CD pipelines explained
- 13:25Testers in automation
- 17:20Branching strategies
- 19:29Regression vs progression testing
- 23:47Manual testing in pipelines
- 28:51CI to CD in production
- 34:53CD deployment considerations
- 38:06Q&A
related talks
36mUsing Jenkins to Build, Deploy, and Automate Projects
48mDemystifying CI/CD
26mIntelligent Deployment Pipelines
22mLet's Build A CI CD Pipeline
01h 12mPitfalls of Continuous Deployment
44mExtending GitHub Flow with Practical Testing
46mIdeal Blueprint Versus Reality for CI/CD Pipelines
55mBuild your APIs and DevOps Hybrid Skills