GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
There was an error fetching the commit references. Please try again later.
@@ -11,4 +11,9 @@ First, the username to authenticate with has to be set using the `AUTH_USER` var
Second, a key pair has to be generated, of which the private key is added as a CI variable `AUTH_KEY` in reposity settings > CI/CD.
The public one has to be added to `~/gitlab-runner/authorized_keys`, where `~` signifies the `AUTH_USER`'s home.
Jobs, which have the variable `SUBMIT_TO_SLURM` set, will have their `script` submitted to SLURM.
Options for SLURM's `salloc` are configurable by setting the respective environment variables preceded by `SLURM_` in the `variables` section of the job definition.
Jobs without `SUBMIT_TO_SLURM` will have their `script` executed on the frontend of the cluster.
An example `.gitlab-ci.yml` file can be found in the root of this repository.
