Morning,
Just getting back to this problem and resolved the problem in less than 30
mins due to your tips/suggestions :) Thank you
Issue was solved by implementing 2 steps:
1. First, by referencing $WORKSPACE when providing the path to the
deploy-script (i.e $WORKSPACE/deploy-script.sh). This by itself, I
suspect, would not have solved my issue but it is a fine code enhancement.
2. Second (and critical) step is a embarrassing. As John Mellor said, I
was attempting to run a .sh file that did not have execute permission.
- Initially thought it wasn't a permission issue because when logged
into WORKER node I can run `deploy-script` (I had set permissions for
`deploy-script` from within the $WORKSPACE directory on WORKER node).
Problem was that I failed to recall that the contents of $WORKSPACE are
replaced each build therefore permissions for `deploy-script` need to be
set from within the directory holding the repo.
I still don't understand why Jenkins creates a tmp directory when sh is
passed a script file but not when sh is passed a command. Will see if I can
find an explanation online. Will post if I do.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ba8a813c-7043-4bfa-979d-93696151b52b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
