Multiple agents for one configuration due to firewall constraints
I am assessing TC for a possible replacement of our Jenkins platform. Due to our infrastructure we will need to support an instance where we potentially need to use two agents for one build configuration. Here is the situation:
Team City would live in Azure
Build agents would live in Azure and possibly one behind our Firewall on our network
Jira lives on our network behind a Firewall (which we cannot open to Azure)
I want TC to update our Jira tickets when a build completes/fails/etc so I am wondering if I configure a TC agent to live behind our firewall to run post build steps from TC so that it could run a powershell script to update Jira once the particular build configuration finishes the build on the Azure build agent. Is this possible?
Another thought is we use a build trigger to run that script via a separate build configuration but I need to be able to pass parameters to this build configuration, is that possible?
I have yet to install TC on a server so I cannot play around with it.
Thanks for the help!
Please sign in to leave a comment.
Ended up writing support, here is the answer if anyone runs into this scenario down the road:
TeamCity has a nice built-in Jira integration, but if your server cannot access Jira, sadly, the integration will not work.
It is not possible to run a build on two agents - a build is fully executed on one agent. But it is possible to create a build chain, where the second build will be executed on the required agent. It is possible to pass parameter values between builds. You can do this with dep. and reverse.dep parameters (see details in this article)