[TIMOB-23926] Hyperloop: Improve Ti SDK handling during CI builds
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2016-09-20T21:42:47.000+0000 |
Affected Version/s | Hyperloop 2.0.0, hyperloop 1.2.7 |
Fix Version/s | hyperloop 1.2.8 |
Components | Hyperloop, Tooling |
Labels | n/a |
Reporter | Jan Vennemann |
Assignee | Jan Vennemann |
Created | 2016-09-19T15:25:10.000+0000 |
Updated | 2018-08-06T17:49:32.000+0000 |
Description
The Jenkins build job for Hyperloop sometimes chokes on a wrong Ti SDK. The CI build always trys to install the latest Ti SDK in conjunction with the
-d
flag to select it afterwards. If the latest Ti SDK is already installed this does nothing and we end up building with the Ti SDK that is currently selected on the build slave, which can be wrong.
PR (master): https://github.com/appcelerator/hyperloop.next/pull/75 PR (1_2_X): https://github.com/appcelerator/hyperloop.next/pull/76
PR's merged. Please update the release-page or send me the correct binary to be displayed. Thanks!
Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.