GitLab HPC Driver issueshttps://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues2023-03-02T11:12:56+01:00https://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues/17Breaking changes in GitLab 17.02023-03-02T11:12:56+01:00Huste, TobiasBreaking changes in GitLab 17.0GitLab Runner ~~14.0~~ 17.0 will introduce breaking changes that also require this implementation to be updated. In principle, the step called `build_script` so far will be renamed to `step_script`.
This was already unintentionally intr...GitLab Runner ~~14.0~~ 17.0 will introduce breaking changes that also require this implementation to be updated. In principle, the step called `build_script` so far will be renamed to `step_script`.
This was already unintentionally introduced in runner version `13.1.0` and fixed in `13.1.1` with this Merge Request: https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/2227
Update: Now this is apparently due in version 17.0. See output of gitlab-runner:
```
WARNING: Starting with version 17.0 the 'build_script' stage will be replaced with 'step_script': https://gitlab.com/groups/gitlab-org/-/epics/6112
```
[GitLab epic here.](https://gitlab.com/groups/gitlab-org/-/epics/6112)2021-04-21https://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues/13Set time limit in Slurm job (automatically)2020-03-17T10:29:31+01:00David Paped.pape@hzdr.deSet time limit in Slurm job (automatically)This would allow for faster access to the cluster if a small time limit is set.
If the user doesn't specify a limit in their `.gitlab.yml` it can be inferred from their projects settings. Unfortunately, there is no variable set by GitLa...This would allow for faster access to the cluster if a small time limit is set.
If the user doesn't specify a limit in their `.gitlab.yml` it can be inferred from their projects settings. Unfortunately, there is no variable set by GitLab that exposes this information.https://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues/6How to access group quotas2020-01-28T10:24:08+01:00Huste, TobiasHow to access group quotasE.g. FWDC has additional quotas. How to make them available via CI/CD on hemera?E.g. FWDC has additional quotas. How to make them available via CI/CD on hemera?https://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues/4Notify SlurmJob::OutputFile of changes in file2019-12-16T11:35:51+01:00David Paped.pape@hzdr.deNotify SlurmJob::OutputFile of changes in fileAt the moment SlurmJob::OutputFile outputs new lines every 100 milliseconds. Can this be improved by using inotify or similar methods?At the moment SlurmJob::OutputFile outputs new lines every 100 milliseconds. Can this be improved by using inotify or similar methods?https://codebase.helmholtz.cloud/fwcc/gitlab-hpc-driver/-/issues/1Security concept2020-12-14T13:26:35+01:00David Paped.pape@hzdr.deSecurity conceptThe program needs a security concept.
For now, all jobs are run in sibling directories without any encapsulation/containerization/... This means that a job, running concurrently with other jobs, can easily access their data. This is a p...The program needs a security concept.
For now, all jobs are run in sibling directories without any encapsulation/containerization/... This means that a job, running concurrently with other jobs, can easily access their data. This is a problem when dealing with jobs that contain sensitive information that must not be made public.
A possible solution might be a pool of cluster users that run incoming jobs in a round-robin manner. Their working directories can be secured using UNIX/LDAP permissions.