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
(FM-6457) Fix Windows CI #200
(FM-6457) Fix Windows CI #200
Conversation
Previously the acceptance tests installed JDK from the chocolatey package repo and pinned the version to `8.0.144`; however, that package now fails to install due to a 404 error in the download. This commit updates the version pin to `8.0.152`, which is the latest stable release and which installs correctly.
The shell string in the it block of the pkcs12 acceptance tests does not include escaped quoting around the path to `keytool` prior to this commit. This causes a failure on windows because the path includes a space. This commit wraps the path to keytool in escaped quotes to resolve the issue.
@michaeltlombardi just to let you know I closed and reopened your PR to enable Appveyor. |
@pmcmaw: Looks like the Appveyor build is broken due to configuration? |
@michaeltlombardi Ive rekicked it. I enabled it without the configuration, it should start looking better in a few mins |
Awesome, thank you! |
No problem thats it now :-) |
Looks like the appveyor build is failing because it's trying to use nixy paths on Windows. :( |
Prior to this commit, the unit tests for java_ks could never pass on windows due to use of linux paths and commands hard-coded. This commit adds a variable for the temp paths in both spec test files and guards against running tests that rely on linux commands on a windows machine.
@pmcmaw: All tests are green now. :) |
These commits fix problems with CI for Windows.