You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.
Will this require a cross-build setup so that all variants are built simultaneously, or will it be possible to have multiple separate build jobs in the same Travis stage with different build parameters that all get released with the same version?
Will this require a cross-build setup so that all variants are built simultaneously
No. The new plugins are simple and (mostly) unopinionated. It should be fairly easy to set up your Travis CI automation based on your requirements, and have the plugins help you with versioning and release notes generation.
Go ahead and try it, and tell us how is it going.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This ticket is prescribe a clean solution for a Scala multi-variant project such as https://github.com/linkedin/isolation-forest. Currently, this project uses Shipkit but the setup is complex (multiple Travis CI stages, disabling various Shipkit tasks - https://github.com/linkedin/isolation-forest/blob/master/.travis.yml#L21). More context: #858
isolation-forest requirements, must-haves:
nice-to-haves:
The text was updated successfully, but these errors were encountered: