That's great! Thanks, Ivan!
I kept my scripts in JSL's resource folder and loading them on the Agent
using "libraryResource".
On Wednesday, July 14, 2021 at 11:21:25 AM UTC-7 kuisat...@gmail.com wrote:
> one more thing if you want to have those scripts shared across pipelines
> you can use
one more thing if you want to have those scripts shared across pipelines
you can use the shared library.
You can define those scripts as resources in the shared library and invoke
them directly
def stdout = bat(returnStdout: true, script: "*groovy -e
'${libraryResource('my-script.groovy'))}'* "
no, it is not possible, the groovy code is executed in the Jenkins
controller by design, it is designed to execute simple logic of
orchestration logic, if you want to execute heavy logic you should do it on
the agents by using steps that run scripts or processes on the agent.
pipeline {
age
This is working for me now, I think the issue was that my groovy file under
/var/ was not camel case so it wasn't finding it (locally it was camel case
but my source control didn't pick up the rename because it used to be name
MyTest.groovy).
On Friday, August 25, 2017 at 11:14:30 AM UTC-4, Mar
Maybe you need a "return this" at the end of the groovy file (as in
https://github.com/docker/jenkins-pipeline-scripts/blob/master/src/com/docker/utilities/AWSSync.groovy
)?
On Fri, Aug 25, 2017 at 9:08 AM red 888 wrote:
> Im trying to wrap my head around shared libraries (with descriptive not
>
