MSYS2 is a fork of Cygwin. Many things that are true in Cygwin are
also true for MSYS2, but not all. The Goal of Cygwin was to create a
Unix-like / Linux-like environment which runs on Windows - as such is
tries to do everything in Linux-like way with very few exceptions.
MSYS2 has the goal of cr
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
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 wrote:
> After all conside
On Sat, Nov 28, 2020 at 6:54 PM Aravind SV
wrote:
> Hello,
>
> I completely agree with Jason about creating that boundary.
>
Indeed. It is better to move various tasks into a version-controlled shell
script/ batch file and to then reference that as a material.
This helps us try the script on a
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 Win
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-
Hi Joel,
There is no way that I know of to specify a particular interpreter for GoCD
Tasks but it isn't something I have ever looked into so it might be
possible.
You are correct that each Task needs to explicitly invoke the child shell
of choice. We use PowerShell rather than MSYS2 bash, but
Hello Jason,
Unfortunately I made no progress on this. Furthermore, this is the only
thing I have to solve/get working before I can start transitioning to GoCD.
The issue is exactly that the custom task command gets passed to `cmd.exe`
on Windows.
Before continuing going down the rabbit hole: I
Hi All,
Very oftenly pipeline cannot be triggered and material update in master
will get hunger for long.
How can I resolve this?
Regards,
Sushma
On Tue, Nov 24, 2020, 10:15 PM Joel Bodenmann wrote:
> I've been testing GoCD today. One of my main requirements is that the
> Windows agent(s) can
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
10 matches
Mail list logo
