Build your JS Pipeline in Incremental Fashion
summary
Argues that projects adopt CI/CD incrementally by starting with auto devops then customizing pipelines, using GitLab CI, Docker and Kubernetes, ESLint, storybook, visual tests and container scanner; shows a real fix where a tampered yarn lock appears and a half day node version bug occurs; demonstrates DAG (directed acyclic graph) jobs to run lint and fixtures earlier so pipelines run much faster — GitLab UI pipeline saves time while SaaS runners build GitLab ~60% of the time; enables review apps.
AI-written summary · about
chapters (5)
related talks
26mOptimizing Your CI Pipelines
57mWorkshop. GitLab + CI/CD + JavaScript = ❤️ (part 2)
02h 47mPipes on Pipelines
50mWhy You Need a Software Delivery Machine
39mRemove your Testing Bottleneck with CI/CD Pipelines
57mWorkshop. GitLab + CI/CD + JavaScript = ❤️ (part 1)
24mReinvent your pipeline with GitLab, Kubernetes, and Amazon EKS
17mShift-Left Security in Practice with Gitlab
