Teamcity how to see the final output of a custom script command line build step

Given the step of building a command line with the following custom script:

msdeploy -verb:sync -source:package='%teamcity.build.projectid%\%WebProjectName%.csproj.zip' 

How can I see which variables were replaced?

I don't see the verbose logging option, which contains the final output for debugging the build server anywhere

+5
source share
4 answers

There is the Parameters tab (available as http://teamcity/viewLog.html?buildId=BUILD_ID&tab=buildParameters , where BUILD_ID should be replaced with the identifier of this assembly) in the assembly overview.

There are parameter values, since they were allowed at the start of the assembly.

This page is also accessible through a pop-up window that appears at the end of the assembly status text in the assembly results line in the assembly configuration overview or in the project view.

0
source

There is a file in [tempdirectory] \ agentTmp called build.start.properties.gz, with something like winrar or 7zip, and there is a file called build.start.properties.

There you can see the parameters used for the assembly, for example,% teamcity.build.projectid%

0
source

In case someone else comes here, then you are probably looking for this file, so your script is not working, I suggest you change

-source: package = '% teamcity.build.projectid% \% WebProjectName% .csproj.zip

"% WebProjectName%"

and include double quotes around your variables if WebProjectName contains spaces that your script may not work.

0
source

If your custom script is running in an environment like Unix, you can use the set -x shell command to print each command before executing

Full explanation here fooobar.com/questions/14732 / ...

0
source

Source: https://habr.com/ru/post/1258855/


All Articles