Executing Powershell script that requires arguments from Jenkins pipeline

Question

I've got a project that looks like this:

project
|
├───src
│       Utility.groovy
│
└───vars
        pipeline.groovy
        script.ps1

In pipeline.groovy I have utility object:

def util = new Utility(this)

and a step that calls util.scriptCall(arg1: "1", arg2: "2", arg3: "3"), which is defined as:

this.context.powershell returnStdout: true, script: ".\\script.ps1 -Arg1 ${args.arg1} -Arg2 ${args.arg2} -Arg3 ${args.arg3} -Workspace ${this.context.env.workspace}"

From everything I've found I'm supposedly invoking this correctly, however I'm getting the following error:

.\script.ps1 : The term '.\script.ps1' 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.

I've got the Powershell plugin installed but the lack of documentation for anything related to Jenkins isn't helping. I've moved script.ps1 into the src folder and even tried making a scripts folder for this with the same results.

Any idea why my invoking a script is getting interpreted as a cmdlet?

It means that it can't find that script in the "current directory" (.). Do you know what the current working directory is when you run that command? If not, maybe you can throw in a pwd or ls or something and try to see the output. Maybe the directory you're in is project and you'll need to call ./src/script.ps1 (PowerShell works fine with forward slashes / btw, in case you want to avoid having to escape backslashes all the time) — briantist
– briantist, Commented Jun 5, 2019 at 15:22
hey thanks for the / info! i was assuming that the workspace for jenkins would have been the vars directory but i'll mess around with the path and see if i can get anything. — starscream_disco_party
– starscream_disco_party, Commented Jun 5, 2019 at 15:29

Moerwald · Accepted Answer · 2019-06-05 15:59:20Z

3

Because the script is not available in the location, where you're trying to invoke the script.

Use the absolute path to invoke the script. If the path includes whitespaces use the call operator (&).

& "absolutePathToScript/script.ps1"

I'm not hundred percent sure, but Jenkins will inject the workspace via $env:workspace (at least it will do so in normal PowerShell build steps), so you be able to invoke the script via:

& "$($env:workspace)/vars/script.ps1"

edited Jun 5, 2019 at 15:59

answered Jun 5, 2019 at 15:45

Moerwald

11.4k10 gold badges54 silver badges92 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

starscream_disco_party Over a year ago

The Workspace was the git repository so I ended up having to just relocate the script. Thanks for the helpful info though!

starscream_disco_party · Accepted Answer · 2019-06-05 19:34:39Z

1

I'm just a ding dong. The Workspace was the Git repo that was getting built. I had to relocate the script to that project and it worked as expected.

answered Jun 5, 2019 at 19:34

starscream_disco_party

3,0346 gold badges28 silver badges44 bronze badges

Collectives™ on Stack Overflow

Executing Powershell script that requires arguments from Jenkins pipeline

2 Answers 2

1 Comment

Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Related