Typically such problems are because the shell script is tested under a
different user account than the one used by Jenkins. This may result in
commands not being found due to different $PATH settings or permission
errors because of different user permissions. It's hard to be more
specific without knowing more about the errors you are seeing.
Eric
On 3/5/2021 12:03 PM, Gil Jensen wrote:
can you tell me why Jenkins would get a different result from the
shell scripts alone?
On Wednesday, March 18, 2020 at 12:25:34 PM UTC-4 Siddhesh Malpani wrote:
Mohan,
Yes of course you can do that. Simply ad the shell script file
name in the 'Execute Shell' step as explained by Derek. Remember
that you've give the path of your file relative to your workspace
directory. Suppose your worskapce dir is 'build-dev' and the shell
script 'patch.sh' is located in a dir 'scripts' under the
workspace. Then you'll have to give it's path as:
./scripts/patch.sh
And you're good to go.
Cheers,
Siddhesh
--
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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c6d9f1a7-ac7a-4e88-9267-ee8ec1386223n%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/c6d9f1a7-ac7a-4e88-9267-ee8ec1386223n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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/ddb470f6-4eac-0cbe-2909-117690147526%40cd-adapco.com.
