If files in repo are encryptet with git-crypt, you need to unlock the repo if tests use these files. Even if repo is unlocked in jenkins-pipeline, it is not unlocked anymore after peass locally cloned it.
So you need a way to provide GIT_CRYPT_KEY, which is used to unlock the repo again after local cloning.
What feature do you want to see added?
If files in repo are encryptet with git-crypt, you need to unlock the repo if tests use these files. Even if repo is unlocked in jenkins-pipeline, it is not unlocked anymore after peass locally cloned it. So you need a way to provide GIT_CRYPT_KEY, which is used to unlock the repo again after local cloning.
Upstream changes
No response