Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
On the project that I’m currently working I have a requirement to run a shell command over some static files prior to check-in into TFS.
Is it possible to use TFS checkin policies to force a developer to run a shell script prior to check-in?
Check-in Policies are designed for this purpose: to check for something in order to “authorize” the check-in.
You’ll find an interesting video here about how to develop one. You’ll see that it’s really easy and once you did your first you will want to customize more TFS.
In you case you will have two options (IMHO):
The first should be the best but it bothers me a bit because it’s not the true purpose of the check-in policies to perform a task upfront, but I can’t think about why it shouldn’t work. And maybe you’ll have to go that way it the second solution is not possible.