Reputation: 6963
TFS Gated Check In Fails due to "has not been mapped"
I have a medium sized solution with 8 projects in it. I've been moving things around to ensure "one-time-one-place". To do this I created a new project and moved a bunch of stuff from other projects to this "Common" project.
When I check in the code, and override the Gated Check In policy... it acted like it had to do a batch build prior to the check in happening. I hadn't see this before, but.... the build failed with tons of "The Item xyz has not be mapped"...
What's best way to fix this? Should I un-map everything in the solution and remap? If so do I just delete the mapping and then try to check in the code without the mapping? Or how do I remap to existing local code that I want to check in..?
Upvotes: 1
Views: 655
Answers (1)
Reputation: 73253
Add the mapping for the new project location in the build definitions's Source Settings page:
Upvotes: 2
Related Questions
- How do I remedy "The breakpoint will not currently be hit. No symbols have been loaded for this document." warning?
- How do I use Assert to verify that an exception has been thrown with MSTest?
- How can we fetch the shelveset name during Gated check-in and assign it to a variable in tfs build task
- Cloaked path not working with gated check-in in TFS build
- TFS 2015 Gated check-in failed due to missing mapping
- Build fail gated check-in TFS 2013
- How to reconcile TFS shelveset correctly after a successful gated check-in on the build agent?
- TFS 2012 Multiple Solutions & Build with Gated Check-in
- TFS Gated Build
- TFS gated check-in for one specific solution, nof for a whole Team Project