sbt: Beyond the Build Tool
summary
Tapjoy runs sbt across 60 repositories, authors 13 internal sbt plugins and open sources 5, and uses sbt tasks to do more than build: push-button release (version bump, test, tag, publish), build and push Docker images, upload artifacts to HDFS, schedule Oozie/YARN jobs, and start/scale services on Marathon. They use plugins like sbt-assembly, sbt-release, sbt-docker-compose and Giter8 templates to standardize projects and report measurable productivity and smaller plugin codebases.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 0:58About Kappa
- 1:58About SBT
- 4:50The Journey
- 5:21The Problem
- 6:54Learning Curve
- 8:27Embrace it
- 8:59Documentation
- 10:04Getting Started Guide
- 11:11Community
- 13:59Ask what depends
- 14:25Single Responsibility Goal
- 15:50SBT Release
- 17:32SBT Docker
- 18:14SBT Twirl
- 18:29Torille
- 19:03Plugins
- 19:54Crossbuilding
- 21:20The Next Step
- 22:40Building with Plugins
- 26:30Why Use sbt
- 28:17sbt scripted
- 28:54clean distribution and delivery
- 30:16sbt workshop
- 30:47Complex plugin development
- 31:00Getrate template
- 31:42TapAdd SBT
- 34:55Create Archetypes
- 35:30Collective Journey
- 35:42Necessity and Discipline
- 36:12Conways Law
- 38:10Project Build Definition
- 39:52Recap
- 40:23Resources
- 40:57Questions
