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

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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more