Hi Ketan,
sorry for the late response. I run the env, but did not get any hints or errors for Gauge/GoCD. I’ve added now the direct path to gauge and the java plugin in the .bash_profile (/Users/admin/.gauge/plugins/:/usr/local/Cellar/gauge/0.6.1/bin:) but the problem is still there. I’ve already modified the start script to get the exit code for 100%: mvn gauge:execute -DspecsDir=specs -Denv=ci rc=$? if [[ $rc -ne 0 ]] ; then echo 'Failed tests'; exit $rc fi …but nothing helped. Cheers, michael Am Samstag, 27. August 2016 05:41:42 UTC+2 schrieb Ketan Padegaonkar: > > > > On Thu, Aug 25, 2016, 2:51 PM Michael Pauli <[email protected] > <javascript:>> wrote: > >> Hi Ketan, >> >> the problem also appears, if I run the script on the go agent. What does >> you mean exactly with the env command? >> > > I mean the `env` executable. Typically under `/usr/bin/env`. > > If the script does not run on the machine successfully, GoCD cannot be > expected to run it successfully. Please ensure that the script exits with > an exit code of 0(zero) to indicate a successful run. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
