Hello, I'm not familiar with MSYS2 so maybe I am missing an obvious point but why is it necessary that the Agent process itself run within MSYS2?
Can the Agent process not just launch a child MSYS2 process if the Job requires it? Regards, Jason On Tuesday, 24 November 2020 at 11:45:22 UTC-5 [email protected] wrote: > I've been testing GoCD today. One of my main requirements is that the > Windows agent(s) can perform builds within MSYS2 (unix environment). > > To get started I've opened an MSYS2 / MinGW64 terminal and pasted the > "Test Drive GoCD" line in there. Everything worked out of the box. The > script properly setup both the server and the agent and everything was > running within MSYS2. I was able to perform builds as per my requirements. > > The next step was to only get the agent running as the server itself is > running on a separate FreeBSD machine. However, when attempting to run the > agent within MSYS2 (MinGW64 shell) I'm presented with this message: > > $ ./bin/go-agent console > Unable to locate any of the following binaries: > > /home/joel/go-agent-20.10.0/bin/../wrapper/wrapper-mingw64_nt-10.0-19042-x86-64 > > /home/joel/go-agent-20.10.0/bin/../wrapper/wrapper-mingw64_nt-10.0-19042-x86-32 > /home/joel/go-agent-20.10.0/bin/../wrapper/wrapper > > To me it seems that the java server wrapper is not finding the binaries > for my particular environment. However, the "Test Drive GoCD" > script/binaries ran without any issues. > > How can I solve this problem? Ultimately I just need to run the go-agent > within MSYS2. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/59a60b7e-3330-43d3-becb-b701e8e22c47n%40googlegroups.com.
