Downloading Build Action Logs
Function
This API is used to download build action logs.
Calling Method
For details, see Calling APIs.
URI
GET /v4/{record_id}/task-log
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
record_id |
Yes |
String |
Definition Build record ID. Constraints N/A. Range Use a 36-character string that includes digits, lowercase letters, and hyphens (-). Default Value N/A. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
task_name |
Yes |
String |
Definition A build task has multiple actions. This parameter defines the order of actions in a build process by linking each numbered action to a stage name. Each build action is named using the format: stageX. X refers to the sequence number of the action in the task. For example, the first action is represented by stage1. Constraints N/A. Range N/A. Default Value N/A. |
|
log_level |
No |
String |
Definition Log level. Constraints N/A. Range ● INFO: info logs ● DEBUG: debugging logs Default Value INFO |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
Definition User token. (The value of the X-Subject-Token response header is the user token.) It can be obtained by calling the IAM service API. For details, seeObtaining an IAM User Token. Constraints Global tenant tokens are not supported. Use a region-level token whose scope is project. Range N/A. Default Value N/A. |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
- |
File |
Definition Obtained file. Range N/A. |
Example Requests
GET https://{endpoint}/v4/2cc26382-b2cb-4234-8eb0-b37d362f4d4c/task-log
Example Responses
None
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
OK |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
