[TIMOB-16895] Add argument to accept analytics deploy type
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2014-05-14T22:41:23.000+0000 |
Affected Version/s | n/a |
Fix Version/s | 2014 Sprint 09, 2014 Sprint 09 Tooling, Release 3.3.0 |
Components | CLI |
Labels | n/a |
Reporter | Praveen Innamuri |
Assignee | Praveen Innamuri |
Created | 2014-04-29T23:00:25.000+0000 |
Updated | 2016-09-16T04:11:12.000+0000 |
Description
With the introduction of VPC environments, Studio might pass in the VPC cluster environment name as the deploy-type, to channel the analytics events for a specific server.
One of the use case is that the user might want to package the app with their STAGING server environment, so that while testing their package app, they would like to receive the analytics even on their staging server, instead of production server.
So, CLI might need to add an additional argument (similar to '--build-type') to take any VPC environment name and set the analytics handler in the SDK. If this argument is not set during the build command, then CLI should fall back to using --deploy-type to assign the analytics environment type.
One of the possible new flag name to set is '--build-type', to carry the environment name to SDK.
All subtasks are closed.
Tested the following command
Actual result
Environment: Mac osx 10.9.3 Mavericks Appcelerator Studio, build: 3.3.0.201405271647 Titanium SDK, build: 3.3.0.v20140530112513 Node.JS Version: v0.10.13 NPM Version: 1.3.2 acs@1.0.14 alloy@1.4.0-beta npm@1.3.2 titanium@3.3.0-beta titanium-code-processor@1.1.1