Hi, the screenshot didn't come through correctly, so it would be good if
you can include that.
>From looking at the XML, If I recall correctly, it might be that you were
using the "legacy"/historical syntax for handling exec commands, but need
to dig a bit more. With this syntax it is somewhat
Ideally, you should add that git repository as a material and move all the
other custom commands into a batch file and then run just that batch file.
If you are not in a position to add the git repository as a material, then
please do move all the remaining custom commands into a batch file and
git pull worked for me by adding git has command and pull as argument
mkdir reports 2>nul
IF DEFINED APP_IR_GENERATOR (%APP_IR_GENERATOR%)
how about this if they have spaces,
how we have to handle them custom command
Thanks for your replies .
On Friday, November 10, 2023 at 11:03:59 AM UTC-6
On Sat, Nov 11, 2023 at 1:35 AM Sri Sai Sruthi JAGANNADDAM <
sjagannad...@mdsol.com> wrote:
> Thanks for the response, its just not git pull, there are also some other
> commands which we are using.
>
Indeed. What I'm asking is about only the "git pull".
Actually, you should also consider
Thanks for the response, its just not git pull, there are also some other
commands which we are using.
On Friday, November 10, 2023 at 11:03:59 AM UTC-6 srir...@gmail.com wrote:
> Btw, why exactly are you pulling a git repo? Have you considered adding it
> as a material to the pipeline?
>
> —
Btw, why exactly are you pulling a git repo? Have you considered adding it
as a material to the pipeline?
— Sriram
On Sat, 11 Nov 2023 at 12:24 AM, Sriram Narayanan
wrote:
> Move that “pull” into an like here :
>
> https://docs.gocd.org/current/configuration/configuration_reference.html#exec
Move that “pull” into an like here :
https://docs.gocd.org/current/configuration/configuration_reference.html#exec
If you edit this custom command in the UI, then keep only the git in the
command, and move the pull into the arguments text area below.
— Sriram
On Fri, 10 Nov 2023 at 9:38 PM,
Here is the screenshot
git pull & mkdir reports 2nul & IF DEFINED APP_IR_GENERATOR
(%APP_IR_GENERATOR%)" are failing as they are not able to recognize git &
mkdir, its not a agent issue because the same agent when attached to the
gocd server running on 21.2 version it works fine but not
It's possibly a side effect of fixing issues with spaces in windows
commands in GoCD 22.2.0: https://www.gocd.org/releases.html#22-2-0
It may be that some of your command tasks were *technically* incorrectly
configured on earlier versions but worked as a side effect of these bugs in
GoCD, and
Looks like the git executable is not on the path for the service account
used for the go-agent.
Please compare the PATH settings between your 21.2 and 23.3 instances.
-- Sriram
On Fri, Nov 10, 2023 at 10:55 AM Sri Sai Sruthi JAGANNADDAM <
sjagannad...@mdsol.com> wrote:
> Could any one please
Could any one please help with this - I am writing to report a challenge
we’ve encountered following our recent upgrade from GOCD version 21.2 to
version 23.3. During our testing phase, we observed that certain pipelines,
which execute on Windows agents, are failing with the following error
11 matches
Mail list logo
