You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guides/troubleshooting/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,19 +11,19 @@ List the builds for an Environment of an App:
11
11
First, find your app name by running:
12
12
13
13
```bash
14
-
$ wpe alpha apps list
14
+
$ wpe apps list
15
15
```
16
16
17
17
Next, find your Environment ID by running:
18
18
19
19
```bash
20
-
$ wpe alpha apps get APP_NAME
20
+
$ wpe apps get APP_NAME
21
21
```
22
22
23
23
Once you have your APP_NAME and ENVIRONMENT_ID, use them in the following command to view your builds:
24
24
25
25
```bash
26
-
$ wpe alpha builds list -a APP_NAME -e ENVIRONMENT_ID
26
+
$ wpe builds list -a APP_NAME -e ENVIRONMENT_ID
27
27
```
28
28
29
29
This command will show you a list of builds. Now, you can find the build logs for a specific build with the ID of the build using the `get` command:
@@ -80,7 +80,7 @@ Note that it is acceptable to have a blank script (i.e. `"wpe-build": ""`), but
80
80
If the branch that you are using GitHub does not match the branch that you have configured for your environment, the platform will not build your software. Double check that the branch configured for the environment matches the branch you're committing to in GitHub:
81
81
82
82
```bash
83
-
$ wpe alpha apps get APP_NAME
83
+
$ wpe apps get APP_NAME
84
84
```
85
85
86
86
This command will list your app and the environment configurations with the branch names.
0 commit comments