Updated Travis CI config to use multiple stages for CI/CD. #19
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
Using Travis stages in this way ensures that all build versions are successful before we publish any artifacts. This is in contrast to the previous version where it was possible, but unlikely, for a new version to be published for the baseline dependencies (Spark 2.3.0 and Scala 2.11.8), even if another build using different Spark/Scala versions failed. **New build pipeline using Travis stages** The first "test" stage runs all build variations in parallel to ensure they succeed. The second "release" stage runs the Shipkit ciPerformRelease command. This uploads the new baseline (Spark 2.3.0 and Scala 2.11.8) artifact to JCenter, pushes another commit to the GitHub repo adding version documentation, bumps the version in the version.properties file, and creates a git tag with the version number. **Other minor changes** I updated the .gitignore and deleted some old build files that accidentally got committed in the past.
|
Here is an example of both the "test" and "release" stages running in series. https://travis-ci.org/github/linkedin/isolation-forest/builds/691634791 |
philozophy
approved these changes
May 27, 2020
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.
Using Travis stages in this way ensures that all build versions are
successful before we publish any artifacts. This is in contrast to the
previous commit where it was possible, but unlikely, for a new version
to be published for the baseline dependencies (Spark 2.3.0 and Scala
2.11.8), even if another build using different Spark/Scala versions
failed.
New build pipeline using Travis stages
The first "test" stage runs all build variations in parallel to ensure they succeed.
The second "release" stage runs the Shipkit ciPerformRelease command. This uploads the new baseline (Spark 2.3.0 and Scala 2.11.8) artifact to JCenter, pushes another commit to the GitHub repo adding version documentation, bumps the version in the version.properties file, and creates a git tag with the version number.
Other minor changes
I updated the .gitignore and deleted some old build files that accidentally got committed in the past.