El Bruno

Good,

excellent post of Neno, where shows us how to use a utility that created jason pricket to create false results for builds in Team Build 2010. This utility can be downloaded from here: TfsCreateBuild.exe and then using the following arguments to the TfsCreateBuild.exe application:

• status: < value > Status of the build (Succeeded, Failed, Stopped, PartiallySucceeded)
• /flavor: < name > Flavor of the build (to track test results against, default: Debug)
• /platform: < name > Platform of the build (to track test results against, default: x 86)
• / target: < name > Target of the build (shown on build report, default: default)
• /localpath: < path > Local path of the solution file. (e.g. Solution.sln)
• /ServerPath: < path > Version Control path for solution file. (e.g. $/ proj/src/app.sln)
• /compileerrors: # Number of compilation errors.
• /compilewarnings: # Number of compilation warnings.
• /analysiserrors: # Number of static code analysis errors.
• /analysiswarnings: # Number of static code analysis warnings.
• /DropLocation: < path > Location where builds are dropped.
• /BuildLog: < path > Location of the build log file. (e.g. \server\folder\build.log)

We can get different results like these where I have tried the different status of the builds

In the following I have forced the number of errors of compilation, warnings, etc.; and in addition you can see that you don’t have access to a Log that it does not exist.

Really interesting to set up scenarios for demos, to fill the DB reporting, etc.

Greetings @ Home

The Bruno