Skip to main content

TFS Build vNext–Build tasks cannot handle spaces in repository path

I’m a big fan of the new build system in TFS. However it’s still a learning process for me. After adding the NuGet Packager task, my build failed with the following error message:

1.  T02:04:25.2941286Z Creating Nuget Arguments:
2.  2016-02-08T02:04:25.3019414Z --ARGS: pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\test1.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
3.  2016-02-08T02:04:25.3029180Z Invoking nuget with pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\test2.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
4.  2016-02-08T02:04:25.3029180Z D:\b\3\agent\worker\tools\NuGet.exe pack d:\b\3\_work\1c61834d\my demo project\NugetSpecs\demo3.csproj.nuspec -OutputDirectory d:\b\3\_work\1c61834d\demo -Properties Configuration=Release -version 2016.2.8.1
5.  2016-02-08T02:04:28.3342844Z pack: invalid arguments.
6.  2016-02-08T02:04:28.3391674Z usage: nuget pack <nuspec | project> [options]
The generated Nuget Pack command is indeed incorrect. Why? Because the task didn’t escape the path to my .nuspec file correctly. As highlighted in yellow, you could see that the path contains some whitespaces. 
I was planning to fix the issue, but thanks to the power of open source, someone already fixed the specific task: https://github.com/Microsoft/vso-agent-tasks/commit/3a7ac0f11ebe17cb110cca904cc8313319c4ad97

But how do I get this updated task on my on premise TFS server?

Here are the steps you need to take:
  • Download and install the TFX command line tool using NPM:
    • npm install -g tfx-cli
  • Before you can use the TFX tool with your on premise TFS server, you have to enable basic authentication:
  • Clone the vso-agent-tasks repository on your local file system
    • Find the path to the task you want to upload
    • In our case this is c:\github\vso-agent-tasks\tasks\NugetPackager
  • Run the TFX tool and specify the path of the specific task
    • ~$ tfx build tasks upload --task-path c:\github\vso-agent-tasks\tasks\NugetPackager
  • You can check that the task is uploaded succesfully by executing the following command
    • ~$ tfx build tasks list

More information:

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