Skip to content

1.Validation Check

Deploying Containers

Users need to complete access and deployment of containers on the server according to the Access Guide, SVN Check Guide or Perforce Check Guide.

Note that currently only Messiah and NeoX resources are supported to start checks by deploying containers on the server.

Rule Scheme

Public Rule Base

There exist many public rules for you to choose in the Public Rule Base, as shown in the image.

![image-20220428144837530](../../use/start-check-img/1.png

Choose the rules you need and import them to your group.

Rules and Rule Scheme

See All Rules for rules available for group.

image-20220428145215473

If you don’t find the engine you need in the tabs, click “Enable Rules” to enable your engine first.

Then activate the imported rules. Of course, if you need to customize rules, click “Create Rule” to create your group rules.

After the needed rules are ready, next is to create a rule scheme. A rule scheme is a collection of rules that avoids the trouble of selecting dozens of rules every time you create a check task.

image-20220428145701501

Click “Create Scheme” to create a check scheme. You can give it a name you like.

image-20220428145851385

After the scheme is created, configure rules for it. Add rules from the group to this scheme.

image-20220428150006229

After creating the scheme and importing rules, you can create a check task.

Creating Check Tasks

There are three methods to create a check task: manual creation on ArtEase, timed task and creation through the interface.

Manual Creation on ArtEase

image-20220428155440119

Click “Run Check” to create a check task.

image-20220428161834188

Generally, you only need to select the mount branch and rule scheme to create a check task. However You can also enter a local SVN branch or expand Advanced Options.

When you choose rule schemes, there is a default set of “All Rules”that does not belong to any scheme you created before. If you choose “All Rules”, all activated local rules will be used to run checks.

Local SVN Branch

Local SVN branches support a situation where one server has multiple branch resources.

If your server checks out two branch resources, main and test, respectively located in /home/niyachen/svn/main and /home/niyachen/svn/test in the directory, the mount branch path should be /home/niyachen/svn, with the mount branch name as trunk.

If you need to check the resources under the test branch, enter “test” for the local SVN branch.

Advanced Options

As compared to local SVN branches, Advanced Options support checks of multiple file directories under one branch.

If the mount path is /home/niyachen/svn/main and you want to run a resource check on the package folder and data folder under this SVN resource directory, enter “Set Subpath” under Advanced Options.

Timed Tasks

Users can set timed tasks to run check tasks in a specified time.

image-20220428170329727

Creating Tasks Through Interface

You can refer to Incremental Check and Full Check Documentation.