The GRAILS_HOME is set but if if remove the /c it runs without error. However it doesn't run the grails command. If I go to the directory "..\go\Agent\pipelines\MyFristPipeLine" and run the command "grails -Dgrails.env=wlprod war" from a cmd it does work.
On Thursday, August 4, 2016 at 8:45:15 AM UTC-4, Aravind SV wrote: > > That's probably coming from Grails now - maybe because GRAILS_HOME is not > set? I usually use Procexp > <https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx> > from Microsoft Sysinternals to check environment variables of a running > process. > > Searching on Google for: "Grails syntax of the command is incorrect" comes > up with a lot of interesting links around this: > > https://github.com/grails/grails-core/issues/8598 > http://www.morkeleb.com/2009/04/04/errors-when-setting-up-grails/ > > http://grails.asia/grails-tutorial-for-beginners-setup-your-windows-development-environment/ > > You need to remember that the environment variables which you see in your > command prompt are not necessarily the same as the ones the GoCD Agent > process sees and that's why it sometimes works on the command prompt but > not through the GoCD Agent. I wish there was an easy way to fix or surface > this kind of issue. Lots of people new to GoCD face this. :( > > Hope that helps, > Aravind > -- 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.
