Azure-pipelines-tasks: FtpUpload task fails with the wrong error message when the protocol is missing from the Server URL

Created on 6 Apr 2017  路  4Comments  路  Source: microsoft/azure-pipelines-tasks

Steps to reproduce:

Add an FTP Upload task
Enter the server name without a protocol: e.g.: ftp.someserver.com
Fill in the other required fields
Save the task
Run the build

Output:
The task fails with a quite unhelpful error message:

##[error]Unhandled: Cannot read property 'toLowerCase' of null

Expected output:
The task editor UI should validate the ServerName that it contains a port or the task should fail with a more useful error message.

CrossPlatform
Source
picture nemesv

Most helpful comment

Hi @nemesv, thank you for reporting this! That was quite a vague error message. I created a pull request for this (#3957) and it should get fixed today.

picture davidstaheli on 6 Apr 2017
❤1 🎉1

All 4 comments

Hi @nemesv, thank you for reporting this! That was quite a vague error message. I created a pull request for this (#3957) and it should get fixed today.

davidstaheli picture davidstaheli on 6 Apr 2017
❤1 🎉1

This is now fixed. Thanks again, Viktor!

davidstaheli picture davidstaheli on 6 Apr 2017

Thanks David for the fix!

nemesv picture nemesv on 6 Apr 2017

FYI: I came across this today.
Adding ftp:// as the protocol sorted it

AndyRace picture AndyRace on 11 Apr 2017
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

MichaelWhiteCodingForFun picture MichaelWhiteCodingForFun  路  3Comments
TheRealEdwardCullen picture TheRealEdwardCullen  路  3Comments
richard-ob picture richard-ob  路  3Comments
NatMarchand picture NatMarchand  路  3Comments
divyesh-parikh picture divyesh-parikh  路  3Comments