Team Foundation Server
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.
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.
It is possible to have both TFVC and GIT in the same TFS project, and when you create a new project you set the default repository and the afterwards you can add the second one.
An important notice about this:
If you run XAML based builds, the build definitions can only use the default repository aka the one you selected when you created the TFS project.
So if you still use XAML, make sure you select the correct repository when you create the project
It is not possible to switch over. At least not officially yet….
UPDATE: MS support has a created a tool that can fix this
If you are stuck on upgrading to TFS 2018 due to the old deprecated XAML based builds, it can be a challenge to see how far you are from the goal of zero XAML builds.
