CodeArts Check
CodeArts Check
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Working with CodeArts Check
- Purchasing CodeArts Check
- Configuring Project-level Role Permissions
- Creating a Task
- Configuring a Task
- Executing a Task
- Viewing Check Results
- Querying Audit Logs
- Reference
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
-
Task Management
- Creating a Check Task
- Deleting a Check Task
- Querying Tasks
- Executing a Check Task
- Stopping a Check Task
- Querying the Status of a Task
- Querying Historical Check Results
- Querying Selected Rule Sets of a Task (Version 2)
- Querying Selected Rule Sets of a Task (Version 3)
- Querying the Check Parameters of a Rule Set (Version 2)
- Querying the Check Parameters of a Rule Set (Version 3)
- Configuring the Check Parameters of a Task
- Modifying the Rule Set in a Task
- Querying Check Failure Logs
- Obtaining the Directory Tree of a Task
- Ignoring Directories of a Task
- Querying Advanced Configurations of a Task
- Configuring Advanced Configurations for a Task
- Issue Management
- Rule Management
-
Task Management
- Application Examples
- Appendixes
- Description
-
FAQs
-
General Issues
- Why Am I Told that a Task Is Running and I Should Try Again Later?
- Why Am I Told that I Don't Have Sufficient Permissions and I Should Check and Try Again?
- Why Am I Told that Cppcheck Cannot Tokenize the Code Correctly?
- Why Am I Told that No Dependency Exists in the Maven Repository?
- Why Am I Seeing Error CC.00070400.500?
- Why Don't I Have Enough Permissions When Clicking a Task Name?
- Why Does a Project with WPF in C# Fail?
- Why Is No Data Displayed After a Task Is Complete?
- Why Does a TypeScript Task Fail with a 404 Error in the Log?
- API Issues
-
General Issues
- Videos
- General Reference
On this page
Copied.
One-stop Issue Fixing
One-stop Issue Fixing with Higher Efficiency
Developers are tired of tools that are not easy to understand, issue distribution that is time-consuming and labor-intensive, and repeated handling of the same alarm in multiple versions. These lead to difficulties in issue analysis and fixing, affecting the initiative for tool use.
CodeArts Check provides the following capabilities to help developers efficiently and smoothly check code.
- Code defects are detected by line and fixed quickly according to the provided guides, including built-in coding specifications, compliant and noncompliant examples, and fix suggestions. Developers do not need to retrain specifications and fix skills.
- Issue owners are automatically matched based on the code commit information, improving the issue distribution efficiency, and enhancing specification and quality awareness of developers.
- The ignored issues that have been handled are automatically synchronized. Therefore, all same false positives in a repository only need to be handled once.
The preceding capabilities improve the efficiency of issue analysis and fixing during practices.
Parent topic: Service Features
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
