Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-10274] Release: ti.cloud - On staging, when releasing SDK build 2.1.1.GA, ti.cloud 2.1.0 and ti.cloud 2.2.0 appears in the module folder

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2012-07-31T22:08:05.000+0000
Affected Version/sRelease 2.1.1
Fix Version/sn/a
ComponentsRelease
Labelsn/a
ReporterWilson Luu
AssigneeNeeraj Gupta
Created2012-07-31T13:28:17.000+0000
Updated2014-06-19T12:42:54.000+0000

Description

Description: In staging, when 2.1.1.GA is pushed out, ti.cloud 2.1.0 appears in commonjs/ti.cloud directory on all platforms. Inside ti.cloud 2.1.0, there are only empty folder directories. Steps to reproduce: 0. Go to staging environment (DNS 184.73.81.90) 1. Remove all modules from the following path: Windows 7: C:/user/tester/AppData/Roaming/Titanium/modules/android/ti.cloudpush/ C:/user/tester/AppData/Roaming/Titanium/modules/commonjs/ti.cloud/ Ubuntu: Home/.titanium/modules/android/ti.cloudpush/ Home/.titanium/modules/commonjs/ti.cloud/ OS X: ~/Library/Application Support/Titanium/modules/android/ti.cloudpush/ ~/Library/Application Support/Titanium/modules/commonjs/ti.cloud/ 2. Remove any instance of the 2.1.1 builds from your sdk folder 3. Wait for 2.1.1.GA to push 4. Check the different module folders from step 1 Actual: ti.cloud 2.1.0 will appear in commonjs/ti.cloud along with ti.cloud 2.2.0 Expected: Only ti.cloud 2.2.0 should appear in commonjs/ti.cloud

Comments

  1. Wilson Luu 2012-07-31

    Closing bug. Was fixed by Max and was able to push successfully for 2.1.1 release.

JSON Source