Submission Workflow

Submission script does the following:

1. caches the credentials of the user
2. commits local changes with user provided commit message
3. commits to remote repository using multiple remotes feature of git
4. executes ajax request to webapp front end for evaluation
5. execution node pulls commit from gitlab and evaluates
6. score and logs are committed to eval/ directory of gitlab repo
7. latest commit is pulled from gitlab remote; thus logs become available to user
8. ajax reply is shown to user in nice format

At present, the execution nodes does not commit the results/ directory to gitlab. But it easily can. In the above listed workflow, that is the only missing step.

references

hub @ github - similar goals code, docs
CS50 approach - Ruby RPM, Shell script
Similar work by Lukas White