Jenkinsfile: Add root repository and submodule repositories as safe directories

[mweisgut]

After the security vulnerability CVE-2022-24765, the latest git version available in ubuntu 20.04 was patched.

With this patch, git checks the owner of the top-level directory and does not perform a git command if the owner is not the current user. This check can be disabled for a repository by adding it as a safe directory, i.e., git config --global --add safe.directory <dir>.

In a current CI run, the user is root, but the files and directories in the cloned Hyrise project directory have the owner 113.

This PR adds the directory of the root repository and the directories of the submodule repositories as safe directories to avoid CI errors of the following kind:

fatal: unsafe repository ('/var/lib/jenkins/workspace/hyrise_hyrise_PR-2448' is owned by someone else)

References

• fatal: unsafe repository (REPO is owned by someone else) with ubuntu 20.04 container actions/checkout#760
• fatal: unsafe repository ('/github/workspace' is owned by someone else) gaurav-nelson/github-action-markdown-link-check#132
• https://stackoverflow.com/questions/71849415/cannot-add-parent-directory-to-safe-directory-on-git
• https://github.blog/2022-04-12-git-security-vulnerability-announced/
• git repo, commit adding the safe.directory check: git/git@0f85c4a
• git repo, commit enabling the safe.directory check: git/git@bb50ec3

[mweisgut]

The Jenkinsfile might be the better place for the fix.

[Bouncner]

So we cannot do anything against having a different user than the dir owner here?

Have to trust you here. 🙂

[mweisgut]

So we cannot do anything against having a different user than the dir owner here?

Have to trust you here. 🙂

There probably is something we can do against having a different user than the dir owner. However, so far, I do not know how to achieve it. Since this problem is currently blocking CI runs, I would use this workaround now to be able to perform CI runs again. The user-owner discrepancy is captured in #2450.