Passing arguments from one job to another


I am new to TeamCity and am in process of evaluating it. I have the following question:

I have buildConfigA which is started with certain system properties and environment variables. I want this configuration to trigger another buildConfigB and pass some or all of these properties to the other job. Is this possible in TeamCity? Does TeamCity handle this requirement differently so that this passing of properties is not required? What is the best practice here?


1 comment
Comment actions Permalink

See section "Triggering a custom build" in documentation:

In brief build script of A build configuration can trigger custom build of B by HTTP with any additional build parameters (properties or environment variables).


Please sign in to leave a comment.