Re: [go-cd] Re: GoCD - Deploy using an artefact rather using git checkout - URGENT please

Hello, In case it helps, I see Jason had responded earlier to something like this: Cheers, Aravind PS: Thanks for helping people, Jason. :) -- You received this message because you are subscribed to the Google Groups "go-cd"

[go-cd] Re: GoCD - Deploy using an artefact rather using git checkout - URGENT please

Hello Prakash, What happens if you add "echo" to the start of the command? Assuming it works as intended, the output of echo should make it clear whether or not the environment variables are expanding properly. Another potential issue is with the way the command is constructed in the Pipeline

[go-cd] Re: GoCD - Deploy using an artefact rather using git checkout - URGENT please

Hello Jason Thanks for your email. If I updated variable manually the command works in agent. I am getting the following error: which does not tell me that is related with populating the variable or not.. *[go] Job Started: 2020-08-10 19:53:21 AEST* *[go] Start to prepare

[go-cd] Re: GoCD - Deploy using an artefact rather using git checkout - URGENT please

Hello Prakash, What do you see in the console output beyond the error message? I believe the raw command should get printed to console which would make troubleshooting easier. Here is an example from the raw output of one of our Pipelines that uses Custom Commands: !!|10:43:38.980 [go] Task:

[go-cd] Re: GoCD - Deploy using an artefact rather using git checkout - URGENT please

Hello Helge We tried using the curl command: 6-DeploySIT1: fetch_materials: no clean_workspace: yes approval: manual environment_variables: app_environment: nonprod verify_repo: verify-repo jobs: deploy: tasks: - exec: