A similar issue/improvement JENKINS-43894 has been reported and fixed for refeference repository path during clone, so it's expected that the reference repository path of submodules also expands the node's environment.
Adding an environment variable to the build node configuration, and then setting the reference repository path under "Advanced sub-modules behaviours" in the job configuration gives following output in the checkout log:
[WARNING] Reference path does not exist: ${REFREPO_PATH}/my_refrepo.git
Originally reported by sixten, imported from: Environment variables not resolved in Pipeline SCM -> Advanced sub-modules behaviours -> Path of the reference repo
- assignee:
gordin
- status: Open
- priority: Major
- component(s): git-plugin
- resolution: Unresolved
- votes: 1
- watchers: 2
- imported: 2025-12-02
Raw content of original issue
A similar issue/improvement JENKINS-43894 has been reported and fixed for refeference repository path during clone, so it's expected that the reference repository path of submodules also expands the node's environment.
Adding an environment variable to the build node configuration, and then setting the reference repository path under "Advanced sub-modules behaviours" in the job configuration gives following output in the checkout log:
[WARNING] Reference path does not exist: ${REFREPO_PATH}/my_refrepo.git
- environment:
Jenkins 2.286, Git plugin 4.7.1