generate all config files #3

New Issue

manuel · 2024-10-26T12:46:24+08:00

manuel commented

2024-10-26 12:46:24 +08:00

once we can generate a conf.json from a toml file we need to automatically generate a few more.

base case: 1 task toml generates 1 conf.json

we also need:

release-conf.json: read stages to run from tasks toml configs (eg. release.stages = ["compile"]) . by default (if release.stages in not specified) we want a complete run that can be used for grading. in particular we want to run joj on all test cases of all submitted tasks (eg. all exercises of a hw). only TT needs to be notified of the result (eg. issue opened in course-joj repo)
conf.json at assignment level, ie going through different tasks. it means for instance compiling and running all tasks of the assignment. this would be called with eg. test(h1): joj submission commit. issue should be opened in student repo.

Note: this would be related to JOJ/JOJ3#68. We probably want a "release scroreboard" vs. a progress scoreboard where.

once we can generate a `conf.json` from a `toml` file we need to automatically generate a few more. base case: 1 task `toml` generates 1 `conf.json` we also need: - `release-conf.json`: read stages to run from tasks `toml` configs (eg. `release.stages = ["compile"]`) . by default (if `release.stages` in not specified) we want a complete run that can be used for grading. in particular we want to run joj on **all** test cases of **all** submitted tasks (eg. all exercises of a hw). only TT needs to be notified of the result (eg. issue opened in course-joj repo) - `conf.json` at assignment level, ie going through different tasks. it means for instance compiling and running all tasks of the assignment. this would be called with eg. `test(h1): joj submission` commit. issue should be opened in student repo. Note: this would be related to https://focs.ji.sjtu.edu.cn/git/JOJ/JOJ3/issues/68. We probably want a "release scroreboard" vs. a progress scoreboard where.

manuel added the

enhancement

label 2024-10-26 12:46:24 +08:00

张泊明518370910136 was assigned by manuel

2024-10-26 12:46:24 +08:00

李衍志523370910113 was assigned by manuel

2024-10-26 12:46:24 +08:00

樊络一521370910049 was assigned by manuel

2024-10-26 12:46:24 +08:00

李衍志523370910113 commented

2025-01-28 05:56:27 +08:00

release-conf.json: read stages to run from tasks toml configs (eg. release.stages = ["compile"]) . by default (if release.stages in not specified) we want a complete run that can be used for grading. in particular we want to run joj on all test cases of all submitted tasks (eg. all exercises of a hw). only TT needs to be notified of the result (eg. issue opened in course-joj repo)

I believe this part is already outdated.

conf.json at assignment level, ie going through different tasks. it means for instance compiling and running all tasks of the assignment. this would be called with eg. test(h1): joj submission commit. issue should be opened in student repo.

This part will be refined in conf-gen later. duplicate with the path problem

> `release-conf.json`: read stages to run from tasks `toml` configs (eg. `release.stages = ["compile"]`) . by default (if `release.stages` in not specified) we want a complete run that can be used for grading. in particular we want to run joj on **all** test cases of **all** submitted tasks (eg. all exercises of a hw). only TT needs to be notified of the result (eg. issue opened in course-joj repo) I believe this part is already outdated. > `conf.json` at assignment level, ie going through different tasks. it means for instance compiling and running all tasks of the assignment. this would be called with eg. `test(h1): joj submission` commit. issue should be opened in student repo. This part will be refined in conf-gen later. duplicate with the path problem

李衍志523370910113 closed this issue

2025-05-25 17:00:50 +08:00

Sign in to join this conversation.