Added upload Travis CI stage that pushes artifacts for all build variants #20
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
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.
I added an "upload" Travis CI stage that runs before the "release" stage.
For each build variant in parallel... The "upload" stage checks if a release is needed using the Shipkit
releaseNeededcommand. If the result indicates a release is needed, then the artifacts are uploaded to Bintray using the current version number.The following "release" stage runs the normal Shipkit release process, which can only upload one artifact. This stage does make a following commit to the git repo with release docs, bumps the version in the
version.propertiesfile, and creates a git tag.