-
Bug
-
Resolution: Unresolved
-
Major
Using docker-slaves, the checkout build phase is ran with commands inside the remoting container (which by change has git) not inside the configured build container.
This is due to git-client to create it's own LocalLauncher vs using the Node's one.
- duplicates
-
JENKINS-21342 CliGitAPIImpl is hard-coded to use LocalLauncher
-
- Closed
-
- is duplicated by
-
JENKINS-53877 sshagent + git checkout on local agent: ssh key not found
-
- Closed
-
-
JENKINS-56076 Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
-
- Closed
-
- is related to
-
JENKINS-46230 git-lfs not working in kubernetes container
-
- Closed
-
- relates to
-
JENKINS-40217 Git plugin can't clone when SSH Agent is enabled with different credentials
-
- Open
-
-
JENKINS-54078 [JEP-210] Exception: Object was recently deallocated when using Git + timeout(activity: true)
-
- Resolved
-
-
JENKINS-51542 Git checkout is slower than the command line execution
-
- Closed
-
- links to
[JENKINS-30600] git isn't run inside build container
Remote Link | New: This issue links to "Proposed fix (Web Link)" [ 13159 ] |
Link |
New:
This issue duplicates |
Workflow | Original: JNJira [ 165712 ] | New: JNJira + In-Review [ 182103 ] |
Remote Link | New: This issue links to "git-client PR 219 (Web Link)" [ 15412 ] |
Component/s | Original: docker-slaves-plugin [ 20839 ] |
Labels | New: docker-slaves |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
git-client plugin do not rely on Launcher/FilePath abstraction but sends the whole GitClient implementation class to remote, making it just impossible to rely on a Launcher from caller. Would need to fully refactor GitClient implementation to run on master.