Creating Plugins Using the New TeamCity Plugin UI Framework
summary
TeamCity 2020.2 ships a new JavaScript API that lets UI plugins integrate with the Sakura single‑page React UI, provides TypeScript/Flow typings, lifecycle hooks and DevTools, and supports bundle.dev.url hot‑reload via a local webpack server. The demo builds a plugin that requests TeamCity REST for committers, queries JetBrains Space for profiles, and renders a React component using placeIds and a plugin constructor; it runs live with incremental recompiles. TeamCity has 399 public plugins but only three marked UI plugins.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:53Ecosystem Overview
- 1:56Current Plugin restrictions
- 3:08What's coming in 20202.2: JS API
- 3:56What's coming in 20202.2: DevTools, Typings, ES6
- 5:28Possible integrations
- 7:04How to start
- 9:04Simple plugin: prerequisites
- 10:32Backend Structure
- 13:49Frontend Structure
- 17:00Frontend: incremental updates
- 17:48Frontend: entry point, PlaceIDs, Plugin Constructor
- 18:50Frontend: Plugin Development Mode
- 23:08Frontend: Plugin Lifecycle
- 24:25Frontend: React in action
- 28:15Summary
- 28:30Q&A
related talks
11mUI Plugin Development
29mBuilding custom Figma plugins to unlock new capabilities
27mBeyond Configurations – Integrations to Supercharge Your CI
26mBackstage Plugin Development: Tales from the Trenches
20mContinuous Workflow
21mThe Evolution of React UI Development
46mWhy Vue Cli Needed a UI and What You Can do With it
38mEmbracing Developer Portals in Software Development