search

halliba / az-pipelines-2-sharepoint

Azure DevOps extension - upload build files to SharePoint Online
GNU General Public License v3.0
9 stars 4 forks source link

[Help needed] ##[error]Input required: failOnEmptySource #4

Closed karolwojcik-eaton closed 2 years ago

karolwojcik-eaton commented 2 years ago

Having successfully set all the parameters I am now getting the following error? I have left the source parameter as empty since I create the text file in the root when I run my script.. Should I be specifying something else? Thank you for help in advance! image image

image image

image image

domeniconicoli commented 2 years ago

I'm getting the same error and the failOnEmptySource parameter is not available on the "Advanced" tab.

image

image

This is probably related to this

halliba commented 2 years ago

Hi,

looks like the Azure Pipelines UI is not using the latest version but the agent does?... That might be a "bug" in Azure DevOps. Anyway I will publish a new version with a workaround ASAP.

Can you please check the extension page of your DevOps organization / Server for the Extension version? And please try to add a new task and check if the option is visible for the new task.

domeniconicoli commented 2 years ago

Hi,

looks like the Azure Pipelines UI is not using the latest version but the agent does?... That might be a "bug" in Azure DevOps. Anyway I will publish a new version with a workaround ASAP.

Can you please check the extension page of your DevOps organization / Server for the Extension version? And please try to add a new task and check if the option is visible for the new task.

yes, the version is fine. I also tried to re-add the task but with no luck :(

image

I'm trying now with the 0.3.1

karolwojcik-eaton commented 2 years ago

HI @halliba the version on the the DevOps org is the latest: image

I also tried to re-add the task on a new pipeline with no luck!

domeniconicoli commented 2 years ago

it works now and I can also see the setting under Advanced! image

thank you @halliba

halliba commented 2 years ago

Acutally i found the problem - there was a difference between the task .json manifest files.. I may have to check my build scripts...

I've published another release v0.3.2. Now the parameter actually shows up and works as expected.