Skip to content
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

Configure Appveyor #29

Merged
merged 3 commits into from
Nov 13, 2019
Merged

Conversation

peagha
Copy link
Collaborator

@peagha peagha commented Nov 6, 2019

Dependabot updated ffi, and I took the opportunity to configure a Windows build to ensure an updated Gem doesn't break the project in Windows.

I had to update Aruba because the older versions have many issues with Windows, e.g.: cucumber/aruba#387 (broken Appveyor build)

I also used a more recent Ruby version because some Aruba dependencies wouldn't work with older Rubies: https://ci.appveyor.com/project/peagha/forca/builds/28644278

We have the option not to configure Appveyor for the first edition of the book, because it requires a recent Ruby version. IMO having a green Windows build is better than having Ruby 1.9-2.2 support

@hugobarauna you'll need to add Appveyor to the project to enable the builds in this project

Builds both in Windows and in Linux.
@peagha
Copy link
Collaborator Author

peagha commented Nov 6, 2019

@hugobarauna
Copy link
Owner

IMO having a green Windows build is better than having Ruby 1.9-2.2 support
Agree

@hugobarauna you'll need to add Appveyor to the project to enable the builds in this project

Done. At least I think it's done, it's my first time using Appveryor. How can we check if it's working or not? Should we merge this PR and see if it triggers a build of the master branch?

Aruba doesn't work properly in Windows in the older versions. This PR
adds Windows to the build matrix and updates Aruba to ensure the build
is green.
@peagha peagha merged commit adfb853 into hugobarauna:master Nov 13, 2019
@peagha peagha deleted the configure-app-veyor-master branch November 13, 2019 02:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants