TFS 2017 – how build/deliver only changed files?

by

Lets assume how I solved this problem (if anyone has similar problem):

Since TFS 2017 always delivered all files – changed and unchanged, but I need only changed, I solved this as follows:

Since files that are transferred to Artifact keep timestamp (unchanged files have last_edited timestamp, and edited files have new, current timestamp) I decide to create FIXED Artifact directory (not depending on build version, but always the same). Then I wrote PowerShell script (as a first Release step ) which deletes all files (recursive) which have timestamp that is < (Now – x min), and all empty directories after that.
On this way Artifact directory contains of ONLY CHANGED files (entire file structure (of changed files) is kept). Now Release will deliver only these files to destination.

Cheers! 🙂

More Related Contents:

  1. When should you branch?
  2. How can I use ClearCase to “add to source control …” recursively?
  3. Why is a 3-way merge advantageous over a 2-way merge?
  4. Using IPython / Jupyter Notebooks Under Version Control
  5. ClearCase advantages/disadvantages [closed]
  6. Should I store generated code in source control
  7. What is the cleverest use of source repository that you have ever seen?
  8. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  9. Source control vs. Revision Control?
  10. What’s the best three-way merge tool? [closed]
  11. Storing third-party libraries in source control
  12. Mercurial for Beginners: The Definitive Practical Guide
  13. Named Branches vs Multiple Repositories
  14. Mercurial — revert back to old version and continue from there
  15. Is version control (ie. Subversion) applicable in document tracking? [closed]
  16. Mercurial Subrepos – How do you create them and how do they work?
  17. How to edit incorrect commit message in Mercurial? [duplicate]
  18. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  19. Mercurial: How to ignore changes to a tracked file
  20. How do I perform a recursive checkout using ClearCase?
  21. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  22. Is there a way to keep Hudson / Jenkins configuration files in source control?
  23. Branching Strategies [closed]
  24. Comparison between Centralized and Distributed Version Control Systems [closed]
  25. Mercurial: Merging one file between branches in one repo
  26. How often to commit changes to source control? [closed]
  27. Do you continue development in a branch or in the trunk? [closed]
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment