CODEWITHSUNDEEP
tfs
Prakash
Prakash

Reputation: 103

Gated checkin at client side

We are doing gated-in using TFS. So, what happens is whenever there is check-in, the build process will run for an hour in the build server and after that it will report the build failure results, even it is a simple issue.

If there is a four simple issues, each issue shown after an hour means on each issue fix, the other issue is shown up, then it takes four hours for him.

I would like to know whether, there is any tool which can validate style-cop issues and code-analysis at client side (developer machine) not in the build server. when the developer triggers the check-in.

The process should be like,

Developer check-in the code, validated for style-cop and code-analysis issues at client side (developer machine), once client side (developer machine) validation is over then the entire code changes has to be checked in to the build server.

Upvotes: 1

Views: 216

Answers (2)

Rassi
Rassi

Reputation: 1622

You should look into check-in policies, as these are checks which automatically run before being allowed to check in.

Either create your own custom check-in policy (old article, but still good introduction) or possibly look at this policy which can run StyleCop checks

Upvotes: 1

Aghilas Yakoub
Aghilas Yakoub

Reputation: 29000

Yes exactly i suggest you to execute Style Cop in Visual Studio , right click on your solution and select link Run Style Cop. (Same Case for Code Analysis, click link 'Run Code Analysis on Solution') Ensute that you have copied Setting File Style Cop in the root of each project. For Code Analysis, right click on your project, select properties, access to Code Analysis Tab.

You don't need to create Shelveset on server with Gated Check In, but every developper must realize this work

Upvotes: 0

Related Questions