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 support #628

Closed
Julian-O opened this issue Aug 8, 2017 · 0 comments · Fixed by #931
Closed

Configure Appveyor support #628

Julian-O opened this issue Aug 8, 2017 · 0 comments · Fixed by #931
Labels
tests Related to individual tests in the test suite or running the test suite.

Comments

@Julian-O
Copy link
Contributor

Julian-O commented Aug 8, 2017

MoviePy is currently test using continuous integration using Travis-CI. That is excellent, but Travis-CI only supports Linux and OSX (and is only being deployed with Linux.)

As a result, a number of OS-dependent bugs crept in, and MoviePy did not run on Windows.

PR #626 attempts to address these issues, and hopefully means MoviePy is compatible with Windows now, but to prevent it sliding backwards, it is necessary to add CI testing on Windows.

AppVeyor.com provide a very similar service to Travis-CI.org - CI testing of a matrix of machines based on a YAML script. Like Travis-CI it is free for public GitHub repositories.

#626 includes a working script for AppVeyor that passes (and even runs more code than Travis!) However, an Appveyor account needs to be created and associated with the Zulko/moviepy project and configured to ensure all pull requests and commits are automatically tested, similar to the Travis-CI layer.

@Julian-O Julian-O changed the title Add Appveyor support Configure Appveyor support Aug 8, 2017
@keikoro keikoro added the tests Related to individual tests in the test suite or running the test suite. label Nov 25, 2017
@Overdrivr Overdrivr mentioned this issue Mar 27, 2019
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Related to individual tests in the test suite or running the test suite.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants