From ccfbbbea5d67d49a16253729f88dc3d367e7b06d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9D=8E=E8=A1=8D=E5=BF=97523370910113?= Date: Sun, 15 Sep 2024 23:18:56 +0800 Subject: [PATCH] Update doc: conf.toml detail --- doc%3A-conf.toml-detail.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc%3A-conf.toml-detail.md b/doc%3A-conf.toml-detail.md index ec49c91..5ebb4c1 100644 --- a/doc%3A-conf.toml-detail.md +++ b/doc%3A-conf.toml-detail.md @@ -1,14 +1,14 @@ `conf.toml` file contains the details of steps that should be executed to the newly pushed code. This file will be placed in the repo of each student. The `conf.toml` file will begin with: -``` +```toml logLevel = -4 sandboxExecServer = "172.17.0.1:5051" ``` which helps logging into the server. In the file, there will be many stages stating each parser to run. To be more specific, the parsers below: -``` +```markdown - clangtidy - cppcheck - cpplint @@ -22,7 +22,7 @@ In the file, there will be many stages stating each parser to run. To be more sp During the `run-joj` process, we will have **several stages** where we will apply different parsers to the code. Those **stages and parsers** are what the users should know how to set. The sandbox executor always sends to go-judge. Stages run one by one. Each stage contains an executor that runs command and give the command output, and a parser that parse the output and generate score and comment. Here are the template code for stages and parsers: -``` +```toml [[stages]] name = "" # stage name here [stages.executor]