-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
WIP: Move unsupported platform failure from os.name to separate method. #179
base: master
Are you sure you want to change the base?
Conversation
Previously we've accidentally depended on the isWindows check to see if we're on a supported platform or not, this had the unfortunate side-effect that even with `download = false` we triggered the error(). See #178
name.contains("sunos") -> "sunos" | ||
else -> error("Unsupported OS: $name") | ||
else -> "unsupported" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like this since if we're extending this or someone uses their own distribution URL which does have binaries it's going to fail, and we're providing no way to override it.
Hmm, this wasn't enough, there's still issues
|
This is not ideal since even if `download = true` there could very well be builds that work fine, especially if you're excluding the tasks from the node plugin. But right now there's harder to diagnose errors appearing further down the line and this should make for a more stable build, at least an overall more stable build.
this work isn't abandoned, but currently it looks like it might be easier to solve in a different way |
Previously we've accidentally depended on the
isWindows
check to see if we're on a supported platform or not, this had the unfortunate side-effect that even withdownload = false
we triggered the error()I've moved this to
PlatformHelper.failIfUnsupportedPlatform()