Fix travis integration #80
Conversation
…en works on branches tests, I think)
|
@tierra Can you review this please? :) |
|
Build still failing on two of the four scenarios defined, but now we can see what the error was: https://travis-ci.org/WP-API/WP-API/builds/19077435 :) |
|
Oh, excellent! I like the idea to only test against trunk. |
|
Better yet, if we are only testing against trunk, then it would be a good idea to use - - depth=1 (can't remember if it's the right command) when cloning WP so it builds faster. |
Good idea, and yeah, |
|
Well, you can just switch out the clone that fails there with a |
|
Also worth noting that since there's actually official Git repos for core now, I'll push an update to the URLs too. |
|
Cool, I'm going to go ahead and merge this then. :) |
Fix travis integration
3 participants
Travis-CI builds are returning an error about not being able to clone the repo into the plugins folder, I wasn't able to reproduce it locally (copy & paste every line on the output), so instead of cloning again I just changed it to copy the files. It has the advantage that this way it can also build and test pull requests.
Also changed the git repo for WordPress to the official one: http://make.wordpress.org/core/2014/01/15/git-mirrors-for-wordpress/