All About Submit's Final Script Feature

Available centralized final scripts

• SubmitSubversionHook - Maintain a subversion repository of student submissions.
• SubmitPublicTestHook - Automatically request public tests after every submission.
• SubmitPermissionsHook - Enforce safer permissions than the defaults after submission is completed.

Combining multiple scripts

Sometimes it is desirable to have multiple final scripts each perform tasks. It appears that submit only accepts one script, though, so you will need a workaround. The simplest is to create a simple script that calls each other script in sequence. So, for CS 116 for example, it should be possible to have a file /u/cs116/bin/submit_final_script with contents such as:

#!/bin/bash -p

/u/isg/bin/submit/submit_subversion_hook "$@"
/u/isg/bin/submit/submit_pub_test_hook "$@"

Then, /u/cs116/.submitrc would contain the directive:

final_script=/u/cs116/bin/submit_final_script

Do not forget to set executable permission on the local script that you're using (e.g., chmod u+x submit_final_script).

(Ab)Use as a command-line front-end to Marmoset and MarkUs

Right now, Marmoset and MarkUs have only a web frontend, which is undesirable. A goal for both systems is to have a command-line interface for students who want one. This feature would allow us to piggyback such behaviour on submit itself (and likely in a very straightforward fashion), allowing students to see a uniform command-line interface for all courses regardless of how things are being treated on the back end.