where to store additional metadata for a build

REST API is great. Currently I am filling up the tags field for a particular build with some metadata that can be later retrieved programatically. Is there a better location to store custom metadata for a particular build run? Tags works okay, but I think that field is intented for humans, and shows up in the GUI on the build history page. It'd be better for me to use a storage location which is not shown on the GUI.

4 comments
Comment actions Permalink

One possible way is to publish metadata in build hidden artifacts, i.e. under .teamcity directory.

0
Comment actions Permalink

thank you for your reply. How do I make the artifact get published under the .teamcity  directory?

I am using the build script interaction feature, ie:     <echo message="##teamcity[publishArtifacts '${custom.metadata.file}']" />. How do I tell teamcity that this should get published under that .teamcity folder?

0
Comment actions Permalink

Something like this should work:
<echo message="##teamcity[publishArtifacts '${custom.metadata.file} => .teamcity/subdir']" />

publishArtifacts service message supports the same syntax as in TeamCity web interface.

0
Comment actions Permalink

works well, thank you!

0

Please sign in to leave a comment.