CODEWITHSUNDEEP
buildtriggerscontinuous-integrationreleaseteamcity
praskris
praskris

Reputation: 479

Triggering builds across different TeamCity instances

We have multiple groups running their own TeamCity setups inside the firm. My group provides a set of generic libraries that other project groups use in their projects. We use TeamCity to push versions of our libraries to production. What I need is a way to automatically trigger builds on other group's CI system that depend on our libraries once we push a new version to production? I already have have the scripts to upgrade to the latest version etc ready. Right now it is manual, i would like to automate it and have a new build of the dependent projects triggered once we release a version to production. I am looking for a way to push the trigger notification across Teamcity instances.

Upvotes: 3

Views: 946

Answers (1)

Paul Hunt
Paul Hunt

Reputation: 3575

You can trigger TeamCity builds using an HTTP request so you could modify your build script to make the required requests at the end of the build. This does have the downside that you need to hardcode the list of builds that need to be triggered on the remote servers into your build script.

The syntax for the HTTP request is:

http://<user name>:<user password>@<server address>/httpAuth/action.html?add2Queue=<build type Id>

For full details take a look at this page of the TeamCity documentation:

Accessing Server by HTTP

Upvotes: 3

Related Questions