I need to perform intermediate build log parsing at certain points in my build. I have an existing process that I want to pass the team city build file to.
What I’m attempting to do is download the current running build log file (I have already obtained the build id) and save it to a share on the network where my parse process can access it. However, I get an error indicating the file is not available.
<!-- Download TeamCity Build Log as Build.log -->
<get src="$" dest="$">
<credentials username="$" password="$" domain="$" />
Is it possible to dump the build log file while the build is running? It seems the build log file is not available until the build completes, is this correct? I understand you can send Service Messages via the output stream in the build runner of choice but it appears to not support the build log file.
I was also wondering, is there a way to treat the build log file as an artifact? If so, I would be able to send a Service Message to generate the build file as it supports creation of artifacts on the fly.
I know I could split my build into two smaller builds and leverage the build dependency functionality so I can have access to the build log file for build A in build B. However, I'd prefer not to do that if I do not need too.
Edited by: Sean Gilbert on May 27, 2008 6:59 PM
Edited by: Sean Gilbert on May 27, 2008 7:01 PM