-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
When a Git installation is transferred from one host to another, it has the git_exec_path parameter hardened as specified when running make. In other words, the installation is not fully portable unless it is compiled on the same machine or the install directory is kept after installing. Therefore, commands that are based on scripts, such as git submodule do not work.
As a workaround one can set the --exec-path parameter. This would make the automatic installation of git using "extract a *.zip/*.tar.gz archive" useful and allow different versions of git run in parallel on the same machine without having the need to install it on OS level.
git-client-plugin should allow for specifying this parameter as a directory relative to the binary archive extraction root in the Git settings. It should then be passed to any git command as the full absolute path.
To illustrate, here's how it could be configured then:
Label | |
Download URL | http://some.url.to/git-bin-version.tar.gz |
Subdirectory | bin/git |
Exec-Path | libexec/git-core |
If left empty, the parameter should rather not be passed at all.
[JENKINS-29243] Allow for specifying the '--exec-path' parameter
Description |
Original:
When a Git installation is transferred from one host to another, it has the {{git_exec_path}} parameter hardened as specified when running {{make}}. In other words, the installation is not fully portable when it is not compiled on the same machine or the install directory is moved after installing. Therefore, commands that are based on scripts, such as {{git submodule}} do not work. As a workaround one can set the {{--exec-path}} parameter. This would make the automatic installation of git using "extract a *.zip/*.tar.gz archive" useful and allow different versions of git run in parallel on the same machine without having the need to install it on OS level. {{git-client-plugin}} should allow for specifying this parameter as a directory relative to the binary archive extraction root in the Git settings. It should then be passed to any git command as the full absolute path. To illustrate, here's how it could be configured then: {panel:title=Install automatically} |Label| | |Download URL|{{http://some.url.to/git-bin-version.tar.gz}}| |Subdirectory |{{bin/git}}| |Exec-Path|{{libexec/git-core}}| {panel} If left empty, the parameter should rather not be passed at all. |
New:
When a Git installation is transferred from one host to another, it has the {{git_exec_path}} parameter hardened as specified when running {{make}}. In other words, the installation is not fully portable unless it is compiled on the same machine or the install directory is kept after installing. Therefore, commands that are based on scripts, such as {{git submodule}} do not work. As a workaround one can set the {{--exec-path}} parameter. This would make the automatic installation of git using "extract a \*.zip/\*.tar.gz archive" useful and allow different versions of git run in parallel on the same machine without having the need to install it on OS level. {{git-client-plugin}} should allow for specifying this parameter as a directory relative to the binary archive extraction root in the Git settings. It should then be passed to any git command as the full absolute path. To illustrate, here's how it could be configured then: {panel:title=Install automatically} |Label| | |Download URL|{{http://some.url.to/git-bin-version.tar.gz}}| |Subdirectory |{{bin/git}}| |Exec-Path|{{libexec/git-core}}| {panel} If left empty, the parameter should rather not be passed at all. |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Link |
New:
This issue is duplicated by |
Link |
Original:
This issue is duplicated by |
Workflow | Original: JNJira [ 164112 ] | New: JNJira + In-Review [ 181512 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] |