Hi Joel, I can't say for sure that it is possible because I am not familiar with MSYS2.
GoCD's Task is effectively a wrapper around a command that gets passed to (I think) cmd.exe on Windows. Assuming there is a way to launch MSYS2 (and pass it an instruction set) from the command line it should be fairly straight-forward to configure GoCD to launch it as a child process and execute whatever commands need to be executed in that environment. Sorry I can't be more specific. I don't know the specific technology you depend on but the high-level concept I have in mind whenever I need to get GoCD to do something new is "I can make it do anything I can make the computer do from the command line." Hope this helps, Jason On Tuesday, 24 November 2020 at 15:38:01 UTC-5 [email protected] wrote: > Jason, > > Thank you for your reply. > > I am completely new to GoCD. If I can configure the agent to run all tasks > within the MSYS2 / MinGW64 shell then things will work and the agent itself > does not need to run inside MSYS2. > The reason I attempted to run it inside MSYS2 is because I noticed that > then all tasks executed by the agent are executed in the MSYS2 / MinGW64 > shell without any further configuration. > > If I'm able to configure the agent to run each task in the MSYS / MinGW64 > shell I'm more than happy. How can I do that? > > > Best regards, > ~ Joel > > On Tuesday, November 24, 2020 at 8:48:45 PM UTC+1 [email protected] > wrote: > >> 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/2939bcfa-4ec4-45b0-9084-e7f2f800af56n%40googlegroups.com.
