Automating a Big Data Platform with Jenkins
summary
Sanoma replaces a brittle ETL stack with Jenkins-driven pipelines on Hadoop and Hive, switching to Jenkins in 2012 to schedule and version processing and expose self-service to analysts. The platform runs on ~55 nodes with 650 TB of storage, supports 3,000 jobs a day, ~250 dashboard users and ~40 analysts, and ingests ~25 sources into a few hundred Hive tables. Processing uses Titan for ingestion, Jython-style scripts and MapReduce/Cascading, Yarn, Kafka/Storm for realtime, and ClickView for reporting.
AI-written summary · about
chapters (8)
- 0:00Start
- 23:48Levels of Self-Service
- 27:01Lease Parameterize Builds
- 30:33Current State
- 31:33Use Cases
- 36:38Main Takeaways
- 39:20What Are the Dependencies
- 40:16The Dependency Graph Plugin
related talks
38mOperating Jenkins at Scale
38mOperating Jenkins at Scale
49mData Platform Architecture, Evolution, and Philosophy
30mA Journey Introducing Jenkins to Enterprise IT
35mJenkins Scaling and Organization for an Efficient CI
30mA Journey Introducing Jenkins to Enterprise IT
55mContinuous Integration on Steroids
41mBig data as we know it @bol.com
