What I need to be able to do is to either create a build definition that I can run on a scheduled basis (Tuesdays at 9pm for instance) that will only build and/or deploy the Work Items that are in a State of "Ready To Deploy".Or a way to get a list of files to push based on the TFS API.
sweet dee is dating a retarded person megavideo - List of changesets and updating work
In order to do this, you can pass in revisions as arguments, which will generate a diff based on a range of committed revisions.
For Perforce, Review Board stores changeset numbers of a posted change and can use these to associate particular changes with review requests.
Project Description I've created this project as an example of how to retrieve changeset information from TFS 2010 using the TFS API.
The example allows you to retrieve all of the changesets committed to a TFS 2010 source control location between two dates (how to do this).
Team Foundation Build can be configured to include a Team Foundation Build details Web page that can be viewed over the Internet.
Team members can use this Web page remotely to check the status of builds.Thanks, Edit: The way we have it setup now, is that each developer has their own branch and own website, our software is server based and has to be run on a particular server. This is where QA initially does their testing to move an item to the ready to deploy status.When a dev is ready for QA they check in their changes in their branch and merge into the trunk.The diff will be generated and uploaded to Review Board, and the review request information will be updated based on the changeset description.The Excludes all files that match the given pattern from the diff.I have modified the work items and work flows to accomplish the different states, but I am having an issue getting either a build of just the fixes or a list of all the files to push based on the state of the work item.