SBT monorepo and delivery
summary
A concrete monorepo setup used for both OSS and an internal bank with ~60 Scala projects, using git-tag-derived versioning and CI-driven delivery. It uses sbt-dynver for versions, sbt-release-early to publish to OSSRH or Bintray, CircleCI for reproducible builds, and custom sbt plugins to centralize settings and publish to Artifactory; Bintray is used to enable parallel publishes because OSSRH staging is serial. The experience reduced build.sbt clutter and proved a practical workflow for multi-project delivery.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:28Monorepo benefits
- 7:22Open source monorepo
- 10:14sbt monorepo setup
- 16:13Versioning in sbt
- 22:13CI/CD for open source
- 29:57Enterprise CI/CD
- 37:18sbt plugins
- 42:12sbt monorepo best practices
- 43:43Q&A
related talks
40mMonorepo or Polyrepo: What's the Right Choice for You?
25mMicroservices, Monorepos, and the Efficient Build Processes
26mLeveraging SBOMS to Automate Packaging, Transfer, and Reporting of D...
15mPanel discussion: Mono-repo Vs. Multi-repo Vs. Hybrid
34mOrganising Your Code and State for Governance and Self-Service
44msbt-native-packager - package all the things
06mInterview
17mAutomated Side-by-Side Development of Applications for BOSH...