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

Remote nodes unable to checkout code

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • gerrit-code-review-plugin
    • jenkins 2.190.3
      gerrit code review plugin 0.3.7
    • 0.4.1

      Moving to 0.3.7 has broken checkout on remote nodes. They fail reporting unable to checkout the code after a 10 minute timeout.

      In the log on the gerrit server are hundreds of lines saying:

      WARN com.google.gerrit.httpd.ProjectBasicAuthFilter : Authentication failed for Username for 'https: account inactive or not provisioned in Gerrit

      So it appears that the remote node is using the wrong credentials to try to do the checkout.

       

      Reverting to .03.5 and everything works fine

        1. credentials.png
          credentials.png
          11 kB

          [JENKINS-60383] Remote nodes unable to checkout code

          Will Wagner added a comment -

          So looking at this some more, I believe it is the LFS Pull step that is using the wrong credentials. For some reason it previously used to say 'Enabling Git LFS pull' before it started this and did the config core.sparsecheckout.

          Will Wagner added a comment - So looking at this some more, I believe it is the LFS Pull step that is using the wrong credentials. For some reason it previously used to say 'Enabling Git LFS pull' before it started this and did the config core.sparsecheckout.

          Nick Bulleid added a comment -

          I've uploaded a fix for this issue to GerritHub.

          https://review.gerrithub.io/c/jenkinsci/gerrit-code-review-plugin/+/477949

          Nick Bulleid added a comment - I've uploaded a fix for this issue to GerritHub. https://review.gerrithub.io/c/jenkinsci/gerrit-code-review-plugin/+/477949

          Luca Domenico Milanesio added a comment -

          Thanks nickb_carallon looking at your fix right now.

          Luca Domenico Milanesio added a comment - Thanks nickb_carallon looking at your fix right now.

          Luca Domenico Milanesio added a comment -

          Unfortunately, your fix is breaking existing functionality.

          Let me reproduce the problem and see if there is another way to achieve the same result.

          Luca Domenico Milanesio added a comment - Unfortunately, your fix is breaking existing functionality. Let me reproduce the problem and see if there is another way to achieve the same result.

          Luca Domenico Milanesio added a comment -

          I just tried and it works for me. When the build is triggered on a remote host, I see:

          using GIT_ASKPASS to set credentials jenkins-at-gerritci

          In your case I see from your logs:

          using GIT_ASKPASS to set credentials

          Luca Domenico Milanesio added a comment - I just tried and it works for me. When the build is triggered on a remote host, I see: using GIT_ASKPASS to set credentials jenkins-at-gerritci In your case I see from your logs: using GIT_ASKPASS to set credentials

          Luca Domenico Milanesio added a comment -

          Did you set the credentials id on the multi-branch pipeline job?

          Luca Domenico Milanesio added a comment - Did you set the credentials id on the multi-branch pipeline job?

          Will Wagner added a comment -

          We have set username/password credentials on the pipeline job, see uploaded image.

          Out of interest what functionality is broken by our change?

          Will Wagner added a comment - We have set username/password credentials on the pipeline job, see uploaded image. Out of interest what functionality is broken by our change?

          Luca Domenico Milanesio added a comment -

          Can you try to use the Gerrit authenticated URL?

          https://gerrit.mycompany.com/a/myrepo

          Luca Domenico Milanesio added a comment - Can you try to use the Gerrit authenticated URL? https://gerrit.mycompany.com/a/myrepo

          Luca Domenico Milanesio added a comment -

          willwagner the SCM extensions are completely removed in your proposed change. Without those extensions, you won't be able to successfully complete a branch scanning of a medium-sized Gerrit repository.

          Luca Domenico Milanesio added a comment - willwagner the SCM extensions are completely removed in your proposed change. Without those extensions, you won't be able to successfully complete a branch scanning of a medium-sized Gerrit repository.

          Luca Domenico Milanesio added a comment -

          Thanks again willwagner for reporting and fixing the problem.

          Luca Domenico Milanesio added a comment - Thanks again willwagner for reporting and fixing the problem.

            lucamilanesio Luca Domenico Milanesio
            willwagner Will Wagner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: