Help Center/ CodeArts Check/ API Reference/ APIs/ Task Management/ Querying Task Check Failure Logs
Updated on 2023-11-28 GMT+08:00
View PDF

Querying Task Check Failure Logs

Function

This interface is used to query task check failure logs. If execute_id is not transferred, the latest check log is queried.

URI

GET /v2/{project_id}/tasks/{task_id}/log-detail

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID

task_id

Yes

String

Task ID.
Table 2 Query Parameters

Parameter

Mandatory

Type

Description

execute_id

No

String

ID of a single task.

Request Parameters

Table 3 Request header parameters

Parameter

Mandatory

Type

Description

Content-Type

No

String

Setting the Media Type and Encoding Format

X-Auth-Token

Yes

String

User token.

It can be obtained by calling the IAM API (value of X-Subject-Token in the response header).

Minimum: 1

Maximum: 100000

Response Parameters

Status code: 200

Table 4 Response body parameters

Parameter

Type

Description

param_info

ParamInfo object

Task Details

log_info

Array of LogInfo objects

Log information
Table 5 ParamInfo

Parameter

Type

Description

url

String

Repository address

branch

String

Repository Branch

language

String

Repository Language

exclude_dir

String

Excluded Directory

encode

String

Encoding Format

compile_config

String

Compilation Configuration Information

rule_template

String

Rule Set Name
Table 6 LogInfo

Parameter

Type

Description

display_name

String

Log Title

log

String

Log content

level

String

Log level

analysis

String

Logs

faq

String

Cloud Commerce FAQs

Status code: 400

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error Codes

error_msg

String

Description

Status code: 401

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

Error Codes

error_msg

String

Description

Example Requests

GET https://{endpoint}/v2/{project_id}/tasks/{task_id}/log-detail

Example Responses

Status code: 200

Request succeeded!

{
  "param_info" : {
    "url" : "git@xxxxxx_only00001/file.git",
    "branch" : "master",
    "language" : "language",
    "exclude_dir" : "aa",
    "encode" : "",
    "compile_config" : "xxx",
    "rule_template" : ""
  },
  "log_info" : [ {
    "log" : "2023-01-04 14:31:33 Running on server:10.75.***.***\n2023-01-04 14:31:34 waiting subJob to execute\n2023-01-04 14:33:38 flush redis cache successfully!\n2023-01-04 14:33:38 all subJob finish!",
    "level" : "",
    "analysis" : "2023-01-04 14:31:33 Running on server:10.75.***.***\n2023-01-04 14:31:34 waiting subJob to execute\n2023-01-04 14:33:38 flush redis cache successfully!\n2023-01-04 14:33:38 all subJob finish!",
    "faq" : "",
    "display_name" : ""
  } ]
}

Status code: 400

Bad Request

{
  "error_code" : "CC.00000000",
  "error_msg" : "The network is busy. Please try again later."
}

Status code: 401

Unauthorized

{
  "error_code" : "CC.00000003",
  "error_msg" : "The authentication information has expired."
}

Status Codes

Status Code

Description

200

Request succeeded!

400

Bad Request

401

Unauthorized

Error Codes

See Error Codes.

Parent topic: Task Management