You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edit: Instead of parsing the .properties file, we'll parse the .properties.xml file instead implemented by @BlythMeister in #3113
TeamCity provides additional information about the build and the build agent through a text file that is written during the build.
This file contains a number of properties about the build that are not available via environment variables such as configuration parameters.
The location of the file is available during the build in the environment variable TEAMCITY_BUILD_PROPERTIES_FILE and looks something like C:\agentName\t\buildTmp\teamcity.build1035226021699882408.properties.
The file uses the java.util.Properties format (a.k.a. "Property Resource Bundles") and looks like this:
The workaround today is to read the TEAMCITY_BUILD_PROPERTIES_FILE environment variable from the Cake script and parse the file yourself, thus exposing these properties via TeamCityBuildInfo is for convenience.
The text was updated successfully, but these errors were encountered:
Edit: Instead of parsing the
.properties
file, we'll parse the.properties.xml
file instead implemented by @BlythMeister in #3113TeamCity provides additional information about the build and the build agent through a text file that is written during the build.
This file contains a number of properties about the build that are not available via environment variables such as configuration parameters.
The location of the file is available during the build in the environment variable
TEAMCITY_BUILD_PROPERTIES_FILE
and looks something likeC:\agentName\t\buildTmp\teamcity.build1035226021699882408.properties
.The file uses the
java.util.Properties
format (a.k.a. "Property Resource Bundles") and looks like this:I suggest exposing these properties via a name/value collection that returns the value of a property by its name (or
null
if name does not exist).e.g.
The workaround today is to read the
TEAMCITY_BUILD_PROPERTIES_FILE
environment variable from the Cake script and parse the file yourself, thus exposing these properties viaTeamCityBuildInfo
is for convenience.The text was updated successfully, but these errors were encountered: