Set up Windows CI Testing #2477
Labels
Comments
bors bot
added a commit
that referenced
this issue
Aug 15, 2019
3829: ci: add initial appveyor support r=jniles a=jniles Start running a few tests using appveyor to take the pressure of TravisCI. The end goal is to run our tests in two CI environments to speed up the tests and also give us better coverage. For example, right now we only test on Travis on trusty. It would be nice to move over to Bionic or even Windows support as referenced in #2477. Closes #887. Co-authored-by: Jonathan Niles <jonathanwniles@gmail.com>
bors bot
added a commit
that referenced
this issue
Aug 15, 2019
3829: ci: add initial appveyor support r=jniles a=jniles Start running a few tests using appveyor to take the pressure of TravisCI. The end goal is to run our tests in two CI environments to speed up the tests and also give us better coverage. For example, right now we only test on Travis on trusty. It would be nice to move over to Bionic or even Windows support as referenced in #2477. Closes #887. Co-authored-by: Jonathan Niles <jonathanwniles@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A couple of our developers are using Windows as their primary development platform. Since we now have the
cross-envmodule allowing us to use the same script cross-platform, it should be much easier to set up a windows test suite.It looks like we have a couple options: AppVeyor, Shippable. There may be more. Someone should go though, assess these solutions, and see if any of them will work for our context. A bonus if it works with
bors-ng!The text was updated successfully, but these errors were encountered: