[TIMOB-18160] CLI: Implement cURL connectivity tests from titanium-connection-test in ti setup check
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Medium |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2015-01-30T19:11:30.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | CLI |
| Labels | n/a |
| Reporter | Tim Poulsen |
| Assignee | Tim Poulsen |
| Created | 2014-12-09T17:01:39.000+0000 |
| Updated | 2017-03-16T22:27:40.000+0000 |
Description
Add the cURL-based network connectivity tests from the https://github.com/appcelerator/titanium-connection-test project to the
ti setup check functions. Connections should be made via the proxy (if any) as configured with the existing CLI network configuration functionality.
The solution must account for Windows or other systems on which cURL is not installed. The curl executable must be override-able.
If all sites are reachable, output a simple message, like:
✓ cURL connection test
If sites are unreachable, output a message for each site that cannot be access, like:
✕ api.appcelerator.net is unreachable via cURL
PR https://github.com/appcelerator/titanium/pull/177 The cURL commands fail on all platforms now because of invalid usernames/passwords. (The same is true of the titanium-connection-test utility, though it's checks mistakenly show the tests as successful because they don't check results sufficiently.) Regardless, if we supply working user credentials for the tests, those usernames and passwords will be in the public titanium repo , instead of being in the private titanium-connection-test repo.
This functionality will be implemented in the Appc CLI instead.
Closing ticket as the issue will not fix.