-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run start_test.sh on Windows 10 and GitBash #18
Comments
Hi again Stephane, I haven't a Windows 10 under my hand, please feel free to make a PR adding Windows git bash support to the script. I will be glad to review it and add this to the code base. Thanks |
I do next week |
By chance you've finished it yet? |
I faced with the same problem on Windows. |
Thanks @yurchik11 Would you mind to push your Windows git bash version as a new PR to integrate it to the starterkit ? |
@Rbillon59 sorry for the delay, yes sure, but I can't create a new branch. |
Hi, It's because I don't give write access publicly, you would need to fork the repo first Thanks 🙂 |
@yurchik11 I would be really interested in what you changed. can you please describe it? :) |
actually I think I was pretty close,but one path is always changed back to a Windows path. Seems like it is working smooth in a WSL Terminal for me. |
All command
kubectl
do not work on Windows 10 and GitBash.kubectl exec -c jmmaster -i -n "${namespace}" "${master_pod}" -- /bin/bash "/opt/jmeter/load_test"
to
kubectl exec -c jmmaster -i -n "${namespace}" "${master_pod}" -- //bin/bash "//opt/jmeter/load_test"
can you put in variable this part and set if we use this env? (10 occurences)
The text was updated successfully, but these errors were encountered: