Continuous Integration for Node.js with Jenkins
summary
Claims a full CI/CD flow that actually automates integration, tests and delivery for Node.js by running npm install / npm test inside Jenkins, packaging modules and publishing built tarballs to a binary manager. Uses an on‑prem Artifactory as a private npm proxy to avoid public registry outages, stores each build artifact for traceability, and supports Jenkins → Artifactory promotion pipelines so the exact produced package is promoted across environments. Demo shows the pipeline produces and publishes reproducible artifacts.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:21Developer who?
- 0:53What Frog?
- 4:00IF NPM IS A PACKAGE MANAGER
- 6:22Why zips are better
- 14:16Binary Repository as Modules Source
- 20:17Recipe
- 21:29Binary Repository as Deployment Target
- 23:53Versioning By Content
- 24:15Mismatch
- 25:30Git is a Distributed System
- 29:10Meet Artifactory
- 32:11Continuous Integration Automation
- 32:37and show Chuck Norris Quotes.
- 32:52Most Important
- 34:29The Time Machine
- 34:48Quest for Traceability
- 36:17What's the problem?
- 36:47Dependencies Lie
- 37:36Remember? Build Server
- 38:14CI Server is the Single Source of Truth
- 38:31Save the Truth!
- 39:39FIRST RULE OF BINARIES
- 40:38Pre-release version increment in npm
- 42:05Demo Time!
related talks
12mContinuous Deployment in a heavily regulated environment
55mContinuous Deployment Workflows for Modern JavaScript
25mA How I learned to Stop Worrying and Let the Robot Publish to NPM
17mA developer's take on security
20mContinuous Builds with your GitHub projects using Azure Pipelines
36mFrom Zero to Hero: Continuous Delivery and DevOps using GitHub and Azure Pipelines
56mOpening Keynote
47mA universal pipeline for testing web applications using Docker