CliGitAPIImpl is hard-coded to use LocalLauncher

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      We have a custom Jenkins plugin that executes git commands using GitAPI, for example launchCommand("pull", myRemoteRepo, myBranch).
      When a build is launched on a slave the build fails because the git commands attempt to run on the Jenkins master instead of the slave.

      Our workaround was to replace the LocalLauncher created by CliGitAPIImpl with the Launcher provided by Jenkins during setup (using reflection), so that builds on slaves have a RemoteLauncher. It would be preferable to have a constructor in GitAPI that takes an instance of Launcher so that we do not have to code against CliGitAPIImpl directly.

            Assignee:
            Unassigned
            Reporter:
            Rusty Gerard
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: