Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30600

git isn't run inside build container

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          Activity

            This also affects K8N plugin when you use pod+container: 

            podTemplate(cloud: 'kubernetes', containers: [containerTemplate(args: '-c', command: '/bin/bash ', image: 'image with git ca-cert', name: 'base', workingDir: '/home/jenkins')], label: 'base') {
              node('base'){
                container('base')

            {       git credentialsId: 'something', url: '[https://some-ca-cert-git|https://some/].git' }

            }

            cvakiitho Tomas Hartmann added a comment - This also affects K8N plugin when you use pod+container:  podTemplate(cloud: 'kubernetes', containers: [containerTemplate(args: '-c', command: '/bin/bash ', image: 'image with git ca-cert', name: 'base', workingDir: '/home/jenkins')] , label: 'base') {   node('base'){     container('base') {       git credentialsId: 'something', url: '[https://some-ca-cert-git|https://some/].git' } }
            faroguy0 Ian Panzer added a comment -

            Any update on this issue? Encountering it in a k8s environment on AWS.

            faroguy0 Ian Panzer added a comment - Any update on this issue? Encountering it in a k8s environment on AWS.
            markewaite Mark Waite added a comment -

            No change faroguy0

            markewaite Mark Waite added a comment - No change faroguy0

            Are there any plans to actually fix this?

            piotr_niebylski Piotr Niebylski added a comment - Are there any plans to actually fix this?
            markewaite Mark Waite added a comment -

            There have been 3 attempts to fix it. All 3 attempts failed because they were unable to retain compatibility with existing installations and existing code. Additional attempts are certainly welcomed.

            I don't plan to attempt a fix in the next 12 months.

            markewaite Mark Waite added a comment - There have been 3 attempts to fix it. All 3 attempts failed because they were unable to retain compatibility with existing installations and existing code. Additional attempts are certainly welcomed. I don't plan to attempt a fix in the next 12 months.

            People

              Unassigned Unassigned
              ndeloof Nicolas De Loof
              Votes:
              22 Vote for this issue
              Watchers:
              33 Start watching this issue

              Dates

                Created:
                Updated: