/root/.bashrc
will not be overwritten if you change them.set
command ensures that your script will stop on all errors:setup-HOSTNAME
file of the challenge where you want to add a setup script in your code editor.
⇨ Replace HOSTNAME
with your hostname. For example, setup-container
if your host is called container
.setup-HOSTNAME
file.instruqt
. If the learner created the directory, the script returns a success message, and Instruqt continues with the next challenge. If the learner has not created the directory, the script returns a fail message with a hint to the learner, and Instruqt stays at the current challenge.FAIL:
to the stdout
and line 6 sets the exit code to 1, which marks the script as unsuccessful:check-HOSTNAME
file of the challenge where you want to add a setup script in your code editor.
⇨ Replace HOSTNAME
with your hostname. For example, check-container
if your host is called container
.check-HOSTNAME
file.instruqt track test
command, Instruqt CLI starts the track on the Instruqt platform and executes the following challenge life cycle scripts:setup
check
↳ Expect failure since the solve script has not been executed yet.solve
check
↳ Expect success since the solve script has been executed.cleanup
instruqt
:solve-HOSTNAME
file of the challenge where you want to add a solve script in your code editor.
⇨ Replace HOSTNAME
with your hostname. For example, solve-container
if your host is called container
.solve-HOSTNAME
file.cleanup-HOSTNAME
file of the challenge where you want to add a solve script in your code editor.
⇨ Replace HOSTNAME
with your hostname. For example, cleanup-container
if your host is called container
.cleanup-HOSTNAME
file.INSTRUQT_TRACK_ID
INSTRUQT_TRACK_SLUG
INSTRUQT_CHALLENGE_ID
INSTRUQT_PARTICIPANT_ID
INSTRUQT_TRACK_INVITE_ID
INSTRUQT_USER_ID
INSTRUQT_USER_NAME
INSTRUQT_USER_EMAIL
INSTRUQT_PRIVACY_POLICY_CONSENT
#!/bin/bash -l
as the first line to load the environment variables.