We have a custom build which makes use of our build agents multiple times throughout the build process (this was the design of the creator who is no longer at our company). We've just recently discovered that the ActivityLog.AgentScope.Build-Agent-ID.xml logs are being overwritten when the same agent gets used again later on in the process. We end up with only one log, which is from the last instance of the agent being used.
For example, an agent gets called twice during the build process. The first call finishes and the log is there, later on the second call occurs and overwrites the previous log using the same file name (ActivityLog.AgentScope.Build-Agent-ID.xml)
So naturally, we're wanting to retain all logs by adding a timestamp to the log file name. But no where do we see in the custom build where these logs are being created. We've searched through MDSN's Team Foundation Build Activities and the ALM Rangers: TF Build Customization Guide, but with no luck.
We're figuring that build agents weren't meant to be used multiple times in the process of a custom build. But now that we rely on this custom build, is there a way to work around this to keep all of the agent scope logs? We want to avoid reworking the custom build to use an agent only once.
