TeamCity VCS plugin for Diversion version control system.

This is a very rough, basic working version of a Diversion VCS plugin for TeamCity. It does give you first class VCS functionality in TeamCity for Diversion, rather than relying on PowerShell scripts, with change tracking, change details withing TeamCity, patches, server and agent side checkout.

The plugin does not use the Diversion API, it just wraps the dv CLI client so you will need that configured and logged in on your server and build agents.

Currently only tested on Windows on a single main branch.

✅ Working Features:

• ✅ Change Detection: Automatically detects new commits and triggers builds
• ✅ File-Level Changes: Shows actual changed files with status (added/modified/deleted)
• ✅ Server-Side Checkout: Build patches on TeamCity server (requires working directory)
• ✅ Agent-Side Checkout: Full support for dv commands on agents
• ✅ Branch Monitoring: Track specific branches for changes
• ✅ Build Triggering: New commits automatically trigger configured builds
• ✅ Version Display: Shows commit numbers in TeamCity UI

⚠️ Known Limitations:

• ⚠️ Single Branch Only: Each VCS root monitors one branch at a time

• TeamCity 2023.11 or later
• Java 8 or later
• Diversion CLI (dv) installed for change detection

• Diversion CLI (dv) installed and available in PATH
• Diversion authentication configured (dv login must be run)
• Note: Required only if using agent-side checkout mode

1. Download the plugin ZIP from the releases page or build from source
2. Upload to TeamCity: Administration → Plugins → Upload plugin zip
3. Restart TeamCity server
4. Install Diversion CLI on TeamCity server (for change detection, required for both checkout modes)
5. **Clone your Diversion workspace to your server **
6. Configure your VCSRoot (select Diversion from the list, set your repo ID and working directory to the workspace you cloned in the previous step)
7. Run dv login on server
8. For Agent-Side Checkout: Install Diversion CLI on all build agents and run dv login on each agent

mvn clean package

The plugin ZIP will be created at: build/target/teamcity-diversion-vcs.zip

• Repository ID: Your Diversion repository ID (format: dv.repo.<uuid>)
• Branch Name: The branch to monitor (default: main)
• DV Executable Path: Path to dv executable (default: dv)
• Working Directory: Path to your diversion workspace on your server

dv repo

This will display your repository ID in the format dv.repo.<uuid>.

1. TeamCity polls the Diversion repository for new commits
2. Plugin uses dv branch to get the latest commit on the monitored branch
3. Plugin uses dv ls <commitId> <file> to get file-level changes with status codes
4. If new commits are detected, TeamCity triggers configured builds showing actual changed files

Both server-side and agent-side checkout are supported. Choose the mode that best fits your TeamCity configuration:

Server-Side Checkout:

• TeamCity server builds patches and sends them to agents
• Requires Working Directory to be configured in VCS root settings
• Server uses dv checkout to retrieve file contents for patch building
• Agents receive patches and don't need Diversion CLI installed
• Best for environments where installing CLI on agents is impractical

Agent-Side Checkout:

• Agents perform checkout directly using Diversion CLI
• Agent runs dv clone on first checkout
• Subsequent checkouts use dv update and dv checkout for fast incremental updates
• Requires Diversion CLI installed and authenticated on all agents
• Best for distributed teams where agents have full CLI access

TCDiversion/
├── server/              Server-side plugin (change detection, patch building)
├── agent/               Agent-side plugin (workspace checkout)
├── build/               Plugin packaging
├── teamcity-plugin.xml  Plugin descriptor
└── pom.xml             Maven configuration

• Single branch monitoring: Each VCS root can only monitor one branch at a time
• No merge request integration: Does not integrate with Diversion code review features

1. Build the plugin: mvn clean package
2. Copy to TeamCity plugins directory:

   copy build\target\teamcity-diversion-vcs.zip D:\TeamCityData\plugins\

3. Restart TeamCity server
4. Check logs: D:\TeamCity\logs\teamcity-server.log

Contributions are welcome! Please ensure all changes include:

• Updated documentation
• Tested functionality
• Clean commit messages

This project is licensed under the MIT License - see the LICENSE file for details.

For Diversion-specific questions, join the Diversion Discord.

For TeamCity plugin issues, please open a GitHub issue.