-
Notifications
You must be signed in to change notification settings - Fork 31
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
CI Build #80
CI Build #80
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing that might be worth considering is caching certain dependencies like Bundler, the gradle cache for the Android submodule, and maybe Mono - if that makes sense? See: https://docs.travis-ci.com/user/caching/
Otherwise this looks good to me. Setting up Travis for Continuous Delivery sounds like another ticket, but it'd be awesome to get something standard that works across all of our repositories.
Copy-pasta the android .travis.yml cache lines
It's much slower to cache these and is not recommended by travis https://docs.travis-ci.com/user/caching/#Things-not-to-cache
@fractalwrench added caching for bundler/gradle/android following the patterns in bugsnag-android. I added caching of both the mono and unity downloads but it was much slower than downloading them from their original sources so I removed it but made them download in parallel which sped it up slightly. |
This will build the current unitypackage.
We should also configure travis to create the GitHub release and upload the built package. Just need to determine which accounts credentials should be used to do this.