I'm trying to build a Proof of Concept for a CI-CD pipeline at work where we'd take out Jenkins and others to replace it with TC; I'd like to see if what I'm thinking is possible, and if so, how to go about implement it.
Currently we have a Perforce trigger that sends notifications to Jenkins whenever we have a new submit on a specific project. Once Jenkins is notified it triggers a RPM or DEB build of the project, and ships it to our artifact repo.
I'd like to replace it this way, if it's possible, and if so, could you please direct me to the proper documentation ?
First off, my current TC setup:
One TC (2019.2) server
1 RPM builder VM running on CentOS 8, with a TC build agent on it
1 DEB builder VM running on Debian 10.0, with a TC build agent on it
In the future, I'd also have a DockerBuilder VM with a TC build agent on it, but I'm not there yet.
What I'd like is the TC server be aware of a new Perforce changelist being created, and pull the data, send it to both builder VMs, and let each VM create its specific type of package.
Is this possible under TeamCity, and if so, where can I find proper documentation on this. The VMs could be replaced with docker containers, but it's not a must. I already have the VMs up and running.