Create build on release tag #55
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implements my suggestion on #53, when a new GitHub Release is created Travis CI starts a new build and when finished uploads the TFTrue.so binary to the created release.
|
Are you sure this is not going to break the Auto Updater? it directly depends on the tag which has to be a version number. |
|
This only starts the CI when you create a new tag/release on github, so you define the tag/version number. So if you were to happen to create a tag named 4.87 for instance it will trigger the build, and after the build is finished upload TFTrue.so the release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements my suggestion on #53, when a new GitHub Release is created Travis CI starts a new build and when finished uploads the TFTrue.so binary to the created release.