bob
bob copied to clipboard
BobBuildTool
bob jenkins on windows (by msys2)
Just for documentation, because this is ugly and completely NOT intuitive: strange behavior between jenkins and msys2.
http://jenkins:8080/configure --> environment variables name: Path value: C:\msys64\usr\bin;$PATH
Refer the mixed style between windows and linux syntax... Another solution would be, to set the global windows environment, BUT this is in the most cases not a good idea, because overriding stuff like cmd, tar, ...
I have to revert this. just adding this environment variable doesn't work for me. I realized, that I still have msys in Path environment variable. But in different systems, this will not work, e.g. if WSL is installed. Currently I have no solution for that. For executing the generated bash scripts, jenkins have to know a bash.exe. I found no other solution that adding this to env Path.
SOLVED: So I created a new windows user, with got the necessary pathes to msys/usr/bin and to bob!
SOLVED: So I created a new windows user, with got the necessary pathes to msys/usr/bin and to bob!
I think this is somthing that must always be solved by whoever sets up Jenkins on Windows. So this is more a documentation issue. But I did not have a look at Jenkins and Windows yet...
I agree. We should discuss, if it is necessary to develop a native windows support for bob, or we should use MSYS2 as prerequisite (native vs. common single script-language). If MSYS2 will be the solution, we have to document, how MSYS2 have to be configured and used. stuff like:
- using the msys cmd start batch for getting WD env var
- the possibility for sym-links
Maybe both? It should be possible to have a native Bob that uses MSYS to execute bash scripts and Bob could be run directly from MSYS as it is now...
It would be cool if someone could pick this up. In the end it is just about amending the documentation to describe the MSYS2 and native Windows setup in the required detail...
so that is a topic 4 me. we have a working setup here. i will try to describe that!
Fixed long ago by 8e6a87ee4a015fd3dcfa83fa14b03250312013fd which covers native Windows and MSYS2 setup.