TeamCity + MSTest - how to grab the generated artifacts?
I have searched and searched but to no avail.
How to unit test the output of artifacts with TeamCity + MSTest step?
We stuff folders / artifacts in in the test directory - I don't ask about [DeploymentItem] and friends
In particular, we create a bunch of log files as we run tests, and I would like to save them for historical review.
We are currently manually checking the auto-generated TestResults folders as we have multiple build agents and MSTest has a habit of deleting the "Out" folder after it completes.
I tried to disable deployment entirely using the .testsettings file, but MSTest still tries to execute it in its dedicated deployment temp directory - but practically nothing is deployed (you can imagine how well this works)
EDIT:
To be clear, the problem is that MSTest is running one test in folders with hard-to-program predictions, thus making the TeamCity artifact capture next to useless. My question is:
How can you shoot down / predictably find these potential artifacts and then capture them with TeamCity?
source to share
In order to write the files that are output by the TeamCity build process, you need to specify their paths in general settings / artifact roads . For example, to select all files located in a folder named Test Log Files at the root of the agent's help directory, you would do the following:
The captured files will then be stored as artifacts associated with that particular build of the build and can be viewed or downloaded using the build history page:
The length of time artifacts are kept is controlled by TeamCity's cleanup rules.
source to share