-
Notifications
You must be signed in to change notification settings - Fork 99
Move travis to develop branch #88
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
Conversation
Use a passworded zip for the dll's Not entirely sure where to document the password Travis should now set the environment variable ZIPPASSWORD which can then be used to unzip the .dll's I believe this doesn't work with pull requests, as in theory a pull request could just dump env to access the password.
+ Correct mistake in travis.yml + Remove Travis deploy Our custom tagging was causing this to trigger. We can just rely on the custom solution for now! + Catch branches with /'s in their name as that's not a valid filename
Add automatic github deploys
Add Travis CI support to RT2
If we're already on a build tag, we don't need to do anything.
Enhancements to travis release system, hopefully travis should test this merge.
Include information about the build in the release notes and in the zip. This way we can confirm what build people have downloaded.
Include build information in build zip
|
are there any issues or strangeness we need to know about for moving it to develop? Have you hardcoded the branch in anywhere and we will have to change it? After reviewing, looks good to me. |
|
This might be OT, but how did you get GitHub to display
|
|
It's not coupled to branches at all, just this repo, as it uses the branch that the commit was posted to. @Starstrider42 it's part of the github build API, travis is set to build the pull requests and then update github with their status. |
Move travis ci intergration into the develop branch
Travis CI seems to be stable, PR to move it into the develop branch.