Function call working fine in local but not in Azure powershell task

Jose, Midhun 21

When I run my belowpowershell script to call afunction its working fine in local powershell

SetVariables -Wslot $slot

function definition like

function SetVariables($Wslot) {
.....}

but while I run the same powershell Script from a powershell task in Azure build pipeline, getting the below error,

**.ps1 : The term 'SetVariables' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

below are the properties of the Azure powershell task

task version 2.*
under advanced -> use powershell core option is enabled

Accepted answer

Ian Xue 36,751 Reputation points Microsoft Vendor

2020-11-12T06:11:13.977+00:00

Hi,

Where is the function definition? Is it in the same script where you call it? Try moving the definition to the beginning of the script.

Best Regards，
Ian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Jose, Midhun 21 Reputation points

2020-11-12T06:50:16.3+00:00

Hi @Ian Xue ,

this is how the beginning of my script is looking like
[CmdletBinding()]
param (
[string] $DeploymentVersion = "***",
$slot = "all"
)

Function Definitions below

function CreateWFolder($Wslot) {***}

Now I can see the pipeline task is getting completed successfully :)
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

Rich Matheisen 46,711 Reputation points

2020-11-11T19:40:41.993+00:00

What happens if you change the name of the function SetVariables? Looking at that name, it always seems to be used together with 'task.' I'm guessing that this is something specific to Azure and not to Powershell.
Please sign in to rate this answer.
Jose, Midhun 21 Reputation points

2020-11-12T06:06:50.02+00:00

Hi @Rich Matheisen

I tried changing the name of the function to CreateWFolde

but the error whcih I am getting is the same again when I run the powershell script in the same powershell task. and the script was working as expected from the local machine.

: The term 'CreateWFolder' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Jose, Midhun 21 Reputation points

2020-11-12T06:07:04.247+00:00

is this because of some configuration mismatch one thing which I noticed is when the powershell script is ran in the Azure DevOps task below are the details which I could notice. I doubt if the latest version of powershell is being used or not,

Starting: PowerShell Script

==============================================================================

Task : PowerShell
Description : Run a PowerShell script on Linux, macOS, or Windows
Version : 2.170.1
Author : Microsoft Corporation
Help : https://video2.skills-academy.com/azure/devops/pipelines/tasks/utility/powershell

==============================================================================
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Function call working fine in local but not in Azure powershell task

Function Definitions below

1 additional answer

Your answer