Ketan, Unfortunately I have so far been unable to locate the wrapper binaries inside the test drive binary. The test drive ZIP archive appears to contain pre-compiled executables. The Java Service Wrapper binaries are nowhere to be found in there. I had a look at the corresponding repository (https://github.com/gocd-contrib/gocd-trial-launcher) but no Java Service Wrapper binaries are to be found in there either.
Is it possible that the test-drive setup uses different means to start GoCD and therefore doesn't require/use the Java Service Wrapper at all? It appears to be a Go (golang) application. ~ Joel On Saturday, November 28, 2020 at 2:48:23 PM UTC+1 [email protected] wrote: > I believe the windows installers are stripped off the mysys wrapper > libraries to reduce space. You can probably grab the missing files from the > test drive binary and put them in your gocd installation directory. > > - Ketan > > > > On Sat, Nov 28, 2020 at 5:08 PM Joel Bodenmann <[email protected]> wrote: > >> After all considerations, I think the best solution (for me) is to go >> with the original idea to run the agent directly within the MSYS2 >> environment. This would solve a lot of problems and not require me to deal >> with all the extra fuzz. >> >> To clarify: >> >> - The "Test Drive GoCD" bash script for Windows >> (gocd-20.10.0-12356-1212) can be launched inside of MSYS2 and everything >> works >> - Downloading the agent (go-agent-20.11.0) as the generic ZIP archive >> leads to the error reported original when attempting to run it in MSYS: >> >> $ ./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 further investigate I also tried to run the GoCD server (generic ZIP: >> go-server-20.11.0) inside MSYS. The same issue as with the agent is >> arising: The missing wrapper binaries. >> >> Comparing the filesystems between the plain gocd-agent and the >> test-drive-suite I see a lot of differences. I'm no Java developer but the >> wrapper libraries are not present in the test-drive-suite as library files >> like they are with the plain agent or server. I'm no java developer but I >> assume that they have been embedded into the test-drive-suite binaries. >> >> I've checked the `try.sh` script that's used by the test-drive-suite to >> see whether there are some setups happening that allow it to run inside of >> MSYS2 which are missing when attempting to run just the agent. >> Unfortunately, I couldn't find anything suspicious. The test-drive-suite >> has a pre-compiled `run-gocd.exe` binary. >> >> Could anybody tell me where to go from here? >> >> >> Best regards, >> ~ Joel >> On Saturday, November 28, 2020 at 11:54:25 AM UTC+1 Aravind SV wrote: >> >>> Hello, >>> >>> I completely agree with Jason about creating that boundary. >>> >>> About the difference between the server and the agent, I’m not sure, but >>> did you try downloading the zip “installer” option? >>> >>> Regards, >>> 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]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/go-cd/cd07a000-b1eb-49ee-84f0-5f1656137b3en%40googlegroups.com >> >> <https://groups.google.com/d/msgid/go-cd/cd07a000-b1eb-49ee-84f0-5f1656137b3en%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/0aeb9938-1b4b-4e51-b626-44714924392bn%40googlegroups.com.
