MOSS integration #34

New Issue

manuel · 2024-09-10T15:58:20+08:00

manuel commented

2024-09-10 15:58:20 +08:00

For kind of backward compatibility we might want to think of how to handle MOSS. At the moment we don't have any "frontend" as JOJ1 had and we should not have one.

possible options to reflect on:

integrate to joj as a plugin, eg. with moss: h4 submissions (only sent to moss if activated by TT member)
integrate it to teapot
integrate it to gitea.sh
use gitea action attached to submission repo (cf. joj integration)

For kind of backward compatibility we might want to think of how to handle MOSS. At the moment we don't have any "frontend" as JOJ1 had and we should not have one. possible options to reflect on: - integrate to joj as a plugin, eg. with `moss: h4 submissions` (only sent to moss if activated by TT member) - integrate it to teapot - integrate it to gitea.sh - use gitea action attached to submission repo (cf. joj integration)

manuel added the

enhancement

component

parser

labels 2024-09-10 15:58:20 +08:00

王韵晨520370910012 commented

2024-09-11 16:24:07 +08:00

better to integrate into teapot (or somewhere student's can't see.)
if we integrate into joj/gitea actions, since moss return a link to submitted code, eventually students could see what others write

better to integrate into teapot (or somewhere student's can't see.) if we integrate into joj/gitea actions, since moss return a link to submitted code, eventually students could see what others write

manuel commented

2024-09-11 16:25:39 +08:00

sorry, to clarify: git action for the submission repo (not for students repos). for each course we have a repo where all prev submissions are stores (eg. ece482-submissions).

mechanics would have to be implemented somewhere, but triggered by some commit message, eg. moss: h2 commit on the submission repo could launch teapot to send the request to MOSS and open an issue with the link to the report

sorry, to clarify: git action for the submission repo (not for students repos). for each course we have a repo where all prev submissions are stores (eg. ece482-submissions). mechanics would have to be implemented somewhere, but triggered by some commit message, eg. `moss: h2` commit on the submission repo could launch teapot to send the request to MOSS and open an issue with the link to the report

王韵晨520370910012 commented

2024-09-11 16:49:43 +08:00

still seems better to do in teapot...
since the thing moss returns is an "intermediate" result, not something that judgers or teapot can make direct use of

still seems better to do in teapot... since the thing moss returns is an "intermediate" result, not something that judgers or teapot can make direct use of

manuel commented

2024-09-11 16:51:23 +08:00

yes teapot would make more sense. gitea actions would only provide an easy interface...

王韵晨520370910012 commented

2024-09-11 18:29:28 +08:00

so we label this as wontfix and open an issue at teapot's repository instead?

so we label this as *wontfix* and open an issue at teapot's repository instead?

manuel commented

2024-09-11 18:31:12 +08:00

i guess teapot is a big part of joj3 (called it "joj-suite" for install purpose...). lets see what @bomingzh thinks then we can move to teapot if he is fine with it

张泊明518370910136 commented

2024-09-11 19:17:48 +08:00

Do we only need to run MOSS once on all submissions of one homework after due date?

manuel commented

2024-09-11 19:27:41 +08:00

yes but we need to include all prev submissions (from prev years). idea is to push new submissions to the repo, then we're ready to send that whole assignment to moss

manuel commented

2024-09-11 19:31:15 +08:00

a simple independent script run through gitea actions coiuld also work... might not need to go through teapot for that?

张泊明518370910136 commented

2024-09-11 20:15:17 +08:00

a simple independent script run through gitea actions coiuld also work... might not need to go through teapot for that?

Agree. This part is just not related to any other system. Just a script that sends everything stored in the assignment dir to MOSS is enough.

> a simple independent script run through gitea actions coiuld also work... might not need to go through teapot for that? Agree. This part is just not related to any other system. Just a script that sends everything stored in the assignment dir to MOSS is enough.

王韵晨520370910012 commented

2024-09-11 20:50:09 +08:00

so where should the action being invoked, (upon submission) at students repo or (at end of semester) submissions repo?

manuel commented

2024-09-11 22:13:54 +08:00

ideally at the end of each hw all submissions are collected (could be automated by scanning all repos for releases) then pushed to submission repo. then all sent to MOSS. should be relatively straightforward to implement.

the "sent to MOSS" could then be autamatically done through gitea actions

ideally at the end of each hw all submissions are collected (could be automated by scanning all repos for releases) then pushed to submission repo. then all sent to MOSS. should be relatively straightforward to implement. the "sent to MOSS" could then be autamatically done through gitea actions

王韵晨520370910012 added the

wontfix

label 2024-09-12 16:54:35 +08:00

张泊明518370910136 removed the

wontfix

label 2024-09-15 10:02:41 +08:00

张泊明518370910136 removed the

component

parser

label 2024-09-26 04:50:06 +08:00

张泊明518370910136 commented

2025-03-23 06:34:16 +08:00