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
You can authenticate with Appcircle using either Personal Access Token or API Key:
155
+
156
+
#### Using Personal Access Token
147
157
-[Generate a personal access token from the Appcircle dashboard](https://docs.appcircle.io/appcircle-api/api-authentication#generatingmanaging-the-personal-api-tokens)
148
-
- Using the Appcircle CLI, create a full access API token using the following command with the personal access token specified as "pat": `appcircle login --pat="YOUR PERSONAL ACCESS TOKEN"`.
158
+
- Using the Appcircle CLI, create a full access API token using the following command: `appcircle login pat --token="YOUR PERSONAL ACCESS TOKEN"`.
159
+
160
+
#### Using API Key
161
+
-[Create an API Key from the Appcircle dashboard](https://docs.appcircle.io/appcircle-api/api-authentication#api-keys)
162
+
- Using the Appcircle CLI, authenticate with your API Key: `appcircle login api-key --name="YOUR_API_KEY_NAME" --secret="YOUR_API_KEY_SECRET"`.
163
+
- For multi-organization accounts, you can specify an organization: `appcircle login api-key --name="YOUR_API_KEY_NAME" --secret="YOUR_API_KEY_SECRET" --organization-id="YOUR_ORG_ID"`.
164
+
165
+
#### Logout
166
+
- To logout from your Appcircle account, use: `appcircle logout`
167
+
- This will clear your stored authentication token locally
168
+
169
+
#### Authentication Behavior
170
+
- If you're already logged in and try to login again, you'll see a "You are already logged in" message
171
+
- You must logout first before logging in with different credentials
172
+
- Your token is stored locally and will persist until you logout or manually clear it
149
173
150
-
> Your token will be stored internally. You should always revoke your access token if you do not plan to use it in the future.
174
+
> Your token will be stored internally. You should always logout or revoke your access token if you do not plan to use it in the future.
151
175
152
176
### Starting a New Build via the Appcircle CLI
153
177
@@ -167,7 +191,7 @@ Appcircle CLI includes the following improvements for build log downloading func
167
191
- User-friendly animation is displayed: "Waiting for build logs to be prepared..."
168
192
- Support for manual log download with both task ID (`--taskId`) and commit/build ID (`--commitId`/`--buildId`) parameters
169
193
- Automatic fallback to alternative download methods when the primary method fails
170
-
- Log files are saved with descriptive filenames: `build-task-{taskId}-log.txt`
194
+
- Log files are saved with descriptive filenames that include branch name, profile name, and timestamp: `{branchName}-{profileName}-build-logs-{timestamp}.txt`
This command downloads build logs using either a Task ID (preferred) or a Commit ID and Build ID combination. When using the Task ID method, the CLI automatically waits for logs to be ready, checking at 5-second intervals for up to 2 minutes.
12
14
13
-
The downloaded log file will be saved as `build-task-{taskId}-log.txt`or `{buildId}-log.txt` depending on the method used.
15
+
The downloaded log file will be saved with a descriptive name that includes the branch name, profile name, and timestamp: `{branchName}-{profileName}-build-logs-{timestamp}.txt`. If branch name or profile name is not available, they will be replaced with 'unknown'. All special characters in names are replaced with underscores for filesystem safety.
14
16
15
17
## Features
16
18
17
19
- User-friendly animation is displayed while build logs are being prepared
18
20
- Automatically switches to alternative download methods if the primary method fails
19
-
- Logs are saved with descriptivefilenames: `build-task-{taskId}-log.txt` or `{buildId}-log.txt`
21
+
- Logs are saved with descriptive, sanitized filenames that include branch name, profile name, and timestamp
20
22
- Full file path is displayed to easily find log files
21
23
22
24
## Options
23
25
24
26
```plaintext
25
-
--path <string> [OPTIONAL] Path where logs will be downloaded. Defaults to current directory or Downloads folder
26
-
27
-
--taskId <uuid> [METHOD 1] Task ID for the build process
28
-
29
-
--commitId <uuid> [METHOD 2] Commit ID
30
-
31
-
--buildId <uuid> [METHOD 2] Build ID
27
+
--path <string> [OPTIONAL] Path where logs will be downloaded. Defaults to current directory or Downloads folder
28
+
--taskId <uuid> [METHOD 1] Task ID for the build process
29
+
--profileId <uuid> Build profile ID
30
+
--profile <string> Build profile name (alternative to --profileId)
31
+
--branchId <uuid> Branch ID
32
+
--branch <string> Branch name (alternative to --branchId)
Download your artifact to the given directory on your machine.
4
7
5
8
```plaintext
6
9
appcircle build download [options]
7
10
```
8
11
9
-
## Options
12
+
## Artifact Filename
10
13
11
-
```plaintext
12
-
--path <string> [OPTIONAL] The path for artifacts to be downloaded. Defaults to the current directory
14
+
By default, the downloaded artifact will be saved as `artifacts-{timestamp}.zip`, where `{timestamp}` is the current date and time in `YYYYMMDD-HHMMSS` format. This ensures each download has a unique filename.
13
15
14
-
--commitId <uuid> Commit ID of your build
16
+
## Download Path
17
+
18
+
If the `--path` option is not specified, the artifact will be downloaded to your system's `~/Downloads` directory by default.
19
+
20
+
## Options
15
21
16
-
--buildId <uuid> Build ID
22
+
```plaintext
23
+
--path <string> [OPTIONAL] The path for artifacts to be downloaded. Defaults to ~/Downloads if not specified.
24
+
--profileId <uuid> Build profile ID
25
+
--profile <string> Build profile name (alternative to --profileId)
26
+
--branchId <uuid> Branch ID
27
+
--branch <string> Branch name (alternative to --branchId)
-**Commit vs Branch**: When you provide `--commitId`, the system doesn't need branch information since the commit is already specified. When you provide `--branchId`, the system automatically uses the latest commit from that branch.
153
+
154
+
-**Configuration**: If `--configurationId` is not provided, the system uses the first available configuration for the profile.
155
+
156
+
-**No Wait**: The `--no-wait` parameter is useful for automation scenarios where you don't want to wait for build completion. The command returns immediately with task information.
157
+
158
+
-**Auto Download**: The `--download-logs` and `--download-artifacts` parameters automatically download files after build completion. Use `--path` to specify a custom download location.
159
+
160
+
## Learn More
161
+
162
+
- Use `appcircle build profile list` to get available profiles with their UUIDs and names
163
+
- Use `appcircle build profile branch list --profileId <uuid>` to get available branches
164
+
- Use `appcircle build profile workflows --profileId <uuid>` to get available workflows
0 commit comments