Continuous Integration Pipeline Configuration
summary
Tripwire builds a dependency-driven CI pipeline that ingests Gradle dependency reports into Artifactory and a DB, then compares required vs actual TeamCity triggers and calls the TeamCity API to add or remove them automatically. The system manages ~550 builds (some trees >2,400 deps), provides aggregated dependency and change reports, release tagging, selective artifact cleanup, legal third‑party approval and automated escrow kits, and has run with no manual trigger edits for years, keeping the SCM team small and reproducible builds provable.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:40Continuous Integration
- 3:00Tripwire Software
- 4:53Build Process
- 5:22Dependency Graph
- 6:19Continuous Integration Environment
- 7:02Scalable Build Pattern
- 7:42Collapse Build Pattern
- 8:17Publishing Dependencies
- 9:46Aggregate Dependencies
- 10:07Aggregate Report
- 10:33Change Report
- 12:29Release Tagging
- 13:27Firewall
- 14:24Selective artifact cleanup
- 15:50Thirdparty libraries
- 17:27Reporting
- 18:42Escrow kits
- 19:29Trigger validation script
- 20:59Tripwire
- 29:54Where is all this going
- 32:39Questions
- 33:26Branching
- 36:45Micro
- 37:23Release model
related talks
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
34mFrom build to Continuous Delivery in TeamCity
29mContinuous Integration and Continuous Delivery Pipelines: Just the Basics
45mContinuous Workflow (Team Tools)
01h 01mA team's transition to Continuous Delivery
29mFrom scheduled builds to commit triggered pipelines
20mContinuous Workflow
28mHow We Use TeamCity to Build TeamCity at JetBrains