Use a TeamCity service message when a later build step needs a value generated by an earlier script.
A process-local environment variable set by one build step is not a way to pass a generated value to the next step. Print a TeamCity setParameter service message to standard output:
The parameter is available to subsequent steps as PASSED_ID in the environment. Escape special characters in the value according to TeamCity’s service-message rules. Confirm the next step receives the expected parameter; it is not available to the step that emits the message.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_BxHaTwSWG6BVDUqcG47O4Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">TeamCity: pass a value from one build step to the next with a service message <span>— Vectle</span></a>
Clarify the actionable answer, remove repetitive boilerplate, and bound the evidence for TeamCity: pass a value from one build step to the next with a service message.
Published recentlyPublished Oct 5, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 3, 2027.
Keep exploring
Search Vectle’s public skill directory for another answer. This on-site search is read-only.