eletrotupi / tcc/ commit / 38004a3

frontend: give each EAS build profile a channel and compiler caching

Builds had no channel, so an installed build had nothing to receive an
OTA update on, and without a compiler cache every cloud build compiled
the native layer from scratch. The cache env now lives on a shared base
profile the three profiles extend, environments are explicit, and
preview produces a sideloadable APK
Pedro Lucas Porcellis porcellis@eletrotupi.com · 13 days ago 38004a30fcf3fc21f8954a0179705ede8a78a57e Browse files
Parents c8d4206
Changed files
1
Additions
+18
Deletions
-2
frontend/eas.json modified+18 -2
frontend/eas.json
1 1 
{
2 2 
  "cli": {
3 3 
    "version": ">= 18.11.0",
4 4 
    "appVersionSource": "remote"
5 5 
  },
6 6 
  "build": {
7 + 
    "base": {
8 + 
      "env": {
9 + 
        "EAS_USE_CACHE": "1"
10 + 
      }
11 + 
    },
7 12 
    "development": {
13 + 
      "extends": "base",
8 14 
      "developmentClient": true,
9 - 
      "distribution": "internal"
15 + 
      "distribution": "internal",
16 + 
      "environment": "development",
17 + 
      "channel": "development"
10 18 
    },
11 19 
    "preview": {
20 + 
      "extends": "base",
12 21 
      "distribution": "internal",
13 - 
      "environment": "preview"
22 + 
      "environment": "preview",
23 + 
      "channel": "preview",
24 + 
      "android": {
25 + 
        "buildType": "apk"
26 + 
      }
14 27 
    },
15 28 
    "production": {
29 + 
      "extends": "base",
30 + 
      "environment": "production",
31 + 
      "channel": "production",
16 32 
      "autoIncrement": true
17 33 
    }
18 34 
  },
19 35 
  "submit": {
20 36 
    "production": {}
21 37 
  }
22 38 
}