From build to Continuous Delivery in TeamCity

on YouTube ↗34m

" summary

A concrete pipeline built with TeamCity Kotlin DSL that goes from commit to deploy: it packages frontend and backend as Docker images, runs docker-compose system tests against a live environment, pushes images to a registry, and triggers a deployment build marked as deployment. Uses TeamCity features like snapshot and artifact dependencies so frontend/backend builds run in parallel, system tests consume artifacts and deployments cancel on failed dependencies; shows constants for connections, wildcard artifact unpacking, and Kotlin loops to avoid copy‑paste.

AI-written summary · about

" chapters (15)

1. 0:00Introduction
2. 1:05Guestbook demo
3. 3:11CI/CD goal
4. 4:58TeamCity DSL vs XML
5. 7:57System tests setup
6. 10:51Build dependencies
7. 13:05Auto-run triggers
8. 14:37Pipeline test run
9. 15:24Docker publish setup
10. 18:45Private repo fix
11. 21:43TeamCity DSL constants
12. 22:47Deploy config
13. 24:46Final pipeline test
14. 26:01Kotlin DSL improvements
15. 26:48Q&A

" related talks

• 12mHow Development Teams Can Benefit From Working With Tests in a CI/CD (TeamCity example)Evgeny Bovykin · TeamCity – 15 Years of CI
• 32mGame DevOps: Elevating Your Unity and Unreal Build Pipelines With TeamCityDaniel Gallo · JetBrains GameDev Day 2023
• 29mContinuous Integration and Continuous Delivery Pipelines: Just the BasicsAnn Marie Fred · OpenInfra Summit Berlin 2022
• 28mContinuous Integration and Continuous Delivery Pipelines for Beginners and ManagersAnn Marie Fred · cdCon 2022
• 01h 01mA team's transition to Continuous DeliveryAshley Noble · NDC Sydney 2017
• 44mContinuous Integration Pipeline ConfigurationThomas Carlier · swampUP 2017
• 30mModern Continuous DeliveryKen Mugrage · DevOpsDays Copenhagen 2019
• 45mContinuous Workflow (Team Tools)Mikhail Vink · JetBrains Night Seoul 2017