Skip to main content

TFS 2015–The item may not be cloaked because it does not have a mapped parent.

I’m working on replacing the existing build system we use based on XAML Workflow by the new build system introduced in TFS 2015. So far, I really like the experience. Customizing became a lot easier than it was before…

However not everything is perfect. While building a solution I noticed the following error message:

“The item $/Framework en Tooling/Drops may not be cloaked because it does not have a mapped parent.”

clip_image002

Let’s find out what was going on.

  • Open your favorite browser and navigate to the web access portal for your team project
  • Click on the BUILD tab
  • Expand the Build Definition section, right click on the failing Build definition and choose Edit… from the context menu
  • The build definition is loaded. Now click on the Repository tab.
  • On this tab you see the workspace mapping used for the build definition. In my case it looked like this:

clip_image004

  • Seeing this immediately explained the error message. I was cloaking a folder that was on the same level as the folder I was mapping. With the current mapping configuration the Drops folder would never be downloaded to the local workspace, so it didn’t make any sense to cloak it(and that was exactly what the error message was telling me)
  • To fix it, the only thing I had to do was remove the Mapping line from the list
Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more