[TIMOB-24162] Allow custom environments in config.json
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Critical |
| Status | Resolved |
| Resolution | Duplicate |
| Resolution Date | 2019-10-02T05:57:58.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Creative |
| Assignee | Chris Barber |
| Created | 2016-11-17T11:17:29.000+0000 |
| Updated | 2019-10-21T15:41:38.000+0000 |
Description
The current config.json file only allows a specific set of environments. According to the manual, some of these are tightly coupled to running on a 'device' or running on an 'emulator'.
This setup restricts a lot of freedom for the developers. Nor does it provide ease of use, since we cant select a certain config for a certain build.
This might has to do with the
titanium build -D/\-\-deploy\-type command, in how that selects the correct config.
The problem I'm having is that the env:test in my config.json is currently empty because I cant use it. env:test is bound to be used on testing on a device, while i actually want it to run unit tests no matter what target i deploy it onto.
https://wiki.appcelerator.org/pages/viewpage.action?pageId=35620077
Thanks for submitting the request. Our engineering team will consider it.
iOS Simulator and Android emulator builds have a default deploy target of "development". This can be overwritten using the
\-\-deploy-type testCLI option. iOS and Android device builds have a default deploy target of "test". This can be overwritten using the\-\-deploy-type developmentCLI option. You cannot change the deploy type for distribution builds as they will always be production. However, TIMOB-16869 most closely describes the ultimate goal here of decoupling settings from a deploy type. Resolving as a duplicate.