Maintenance Bugfix: Github Actions runner permission fails at multiple runs

[madebyTimo]

Current Behavior

After one run the CI fails in the next run because it can't remove files created by the last run. exapmle failure
The actual solution is to run a cleanup task at the end of every run like you can see here

Expected Behavior

Runs don't fail because they already run once and the folder isn't deleted manually (or by a cleanup task).

DoD

If there is a solution:

• runs don't fail because they already run once
• CI-caching works
• no actual CI fails cause of the described error

If there is no solution:

• related Github Action Issues are checked and documented
• cleanup task is added to all actual CIs
• need of cleanup task is announced to project members
• no actual CI fails cause of the described error

[madebyTimo]

Also problems at login backend

[madebyTimo]

It is a general problem with Github-Actions. Related issues can be found amount many other issues here and there.

As workaround we decided to run the runner as root, so it has all permission. This shouldn't be a problem because jobs are only triggered by team-members and the runner runs on a dedicated VM.

[delvh]

While I am typically not in favor of running programs as root, I can at least understand it in this case.
Should we inform Professor Becker about this?

[madebyTimo]

I don't think we need to do this. It's a dedicated VM only for the runner and the old user also had docker rights which lead to nearly same permissions as root permission