Task fails trying to look for requirements file when not specified

[niwsa]

The task fails on ubuntu 16.04

2017-12-29T06:16:29.9427835Z [command]/home/****/myagent/_work/1/venv/build/bin/pip install -r /home/****/myagent/_work/1/s
2017-12-29T06:16:31.1832209Z Could not open requirements file: [Errno 21] Is a directory: '/home/****/myagent/_work/1/s'

Note: I did not give Pip requirements file path during configuring as its optional and I don't require it.

[dazfuller]

Thanks for raising this, I've had a quick look and can't see anything obvious that would be causing this issue but I'll keep on digging

[dazfuller]

Crazy question, but did you specify the path to the folder with the requirements file or to the file itself?

[niwsa]

@dazfuller The best I can remember is leaving that input from my side empty.

Ok by default it might be looking in the source folder.But what if I don't need a requirements file at all.

[dazfuller]

It's a good point and I've heard that from somewhere else recently. I'll look into making it optional

[dazfuller]

@niwsa I've just published an updated version which fixes the requirements file issue and adds in a test file pattern to help with test discovery. I've got a test build running with no requirements file and it's working for me, but let me know if it sorts out your problem.