Due to the nature of the build and release services in TFS, strange things can happen.
Just discovered that we had some builds that was marked “retained by release”, as usual, but looking at the details pane, there wasn’t any related deployments, so we wasn’t able to delete those builds.
Microsoft have release a hotfix for TFS 2017 and 2018, that fixes potential cross site scripting.
see TFS hotfix
From time to time, it can be handy to use the Team configuration and members in TFS to set permissions in another application.
In part 2 of this little story about storage use in TFS, we had a look at how the storage was consumed by areas. One of the biggest areas are usually related to build jobs.
In the previous article we looked at the TFS storage growth over time.
Now it is time to dive into this and look at what is actually consuming the space.
This is the first post on monitoring storage usage of on-premise TFS.
Often the databases behind TFS is a black boks, where storage just grows, so we will dig into the database behind to see where the bits and bytes goes.
The older SOAP API for work items and test, will be deprecated in TFS 2020, see Deprecate SOAP
