Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    51
  • Users 0 members are here
Related
Options

Groovy Script (ksc_run_groovy) output

EmreNyz

Hi,

After running a Groovy script in an execution step, Is there any way to read the returned output? We have tried some options inside the groovy script like print, println, System.out.println/print function, but we cannot see the result on the execution log, it is directly log into the server log.

Is there any way that will work like "ksc_local_exec" which read the returned response with a token like [EXEC.OUTPUT]? 

Thanks, 

  • Suggested Answer

    0  

    Hi Emre,

    The way groovy script execution works in PPM is that the value returned by the script will be evaluated to see if the script execution should be considered a success:
    - If it's a String, it's expected to be "true"
    - If it's an integer, it's expected to be 0
    - null value is considered success
    - Otherwise it's cast to a Boolean.

    If you want to write some output to the execution step debug log, you can call this from your script:

    debugExeLog.println(...)

    I'm not aware of any easy way ot get result of the execution (except for the simple success/failure). You could write some complex output to some file from your groovy script and later read the file contents in another step to expose it to other special commands. 

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.