${groovy:"python /path/to/your/python/script".execute().text}

${groovy: "python.exe " + configuration.getWorkspaceDir().getAbsolutePath() + "/qbstuff/grabbigSM.py".execute().text}

${groovy: 
def cmd = "python.exe " + configuration.getWorkspaceDir().getAbsolutePath() + "/qbstuff/grabbigSM.py";
logger.info(cmd);
return cmd.execute().text;
}

Hello Robin

I'm also trying to set a variable value through groovy scripts. However, I noticed I can't just return a value like so

variable.setValue(${groovy:
return "new_value"})

My question is, why this returns null instead of the string? While

return cmd.execute().text

works, I don't understand they are both String type, but only one of them actually sets the variable value.

Another question is, how can I return multiple values and put them in the variable as multi-line values, so that I can use them one by one later?

Much thanks!

Since while you are calling variable.setValue(), it is already in a groovy script, and you no longer need to wrap another groovy script ${return "new_value"}, instead just call:
variable.setValue("new_value");

The variable should be able to store multi-line value, as long as your script pass multi-line value.

Hello Robin

I've encountered this problem when I use groovy to call a python script, then use the return value of python script.
The problem is that the groovy script (cmd.execute().text) always gets nothing (null).

In my python script (execute_cmd.py), I've tried print() or return() the value I want, the groovy script still gets nothing.

This is my groovy script in a Batch/shell build step:

${groovy:
def cmd = "python.exe " + configuration.getWorkspaceDir().getAbsolutePath() + "\\execute_cmd.py " + params.get("component");
logger.info("This is the cmd: " + cmd);
def result = cmd.execute().text;
logger.info("This is result: " + result)
return result
}

And if I go into the QB workspace and call a groovy script in the same directory, to call the python script, it will get the print() result from python.
The groovy script only has this hard coded statement:

def cmd = "python.exe execute_cmd.py My_component";
def result = cmd.execute().text
println result;
// result will be the return (print) value from execute_cmd.py

Can you tell me how this is?

Thank you!

Please print value of the evaluated cmd, and run exactly the same command from groovy (like you've done from workspace now) to see if it works.

I did try print, I've tried print as well as return, it doesn't catch the printed value. cmd.execute().text is still null.

The weird thing is, I can retrieve the value if I execute a groovy script on agent directly (without using QB). I just go to the agent where the workspace is, and create the simple groovy script I pasted above, and run it on a cmd window, it will get the print value from python (stored in the groovy def result).

Not sure what happened here Robin.

Update:
What's the recommended way to publish build log of a certain step as artifact (not the whole config run)? If I could get access to the entire build log conveniently, I can just use that instead of using groovy to catch the stdout.

Thanks!

I mean to run exactly the same command (printed out via logger.info("This is the cmd: " + cmd)) from agent console via groovy to see if it works. You are testing "python.exe execute_cmd.py My_component", but not the same command used by QB.

As to publish build log of specific step, it is not supported by QB.