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

Some environment variables are not expanded during git polling

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin

      When setting the git URL to include environment variables, specifically

      ${JOB_NAME}
      

      , and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

      As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.

          [JENKINS-29689] Some environment variables are not expanded during git polling

          Oded Arbel created issue -
          Oded Arbel made changes -
          Description Original: When setting the git URL to include environment variables, specifically ${JOB_NAME}, and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          New: When setting the git URL to include environment variables, specifically '${JOB_NAME}', and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164671 ] New: JNJira + In-Review [ 181673 ]
          Mark Waite made changes -
          Summary Original: Some environment variables are may not be expanded during git polling New: Some environment variables are not expanded during git polling
          Mark Waite made changes -
          Description Original: When setting the git URL to include environment variables, specifically '${JOB_NAME}', and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          New: When setting the git URL to include environment variables, specifically {{'${JOB_NAME}'}}, and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          Mark Waite made changes -
          Description Original: When setting the git URL to include environment variables, specifically {{'${JOB_NAME}'}}, and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          New: When setting the git URL to include environment variables, specifically
          {noformat}
          ${JOB_NAME}
          {noformat}
          , and "Force polling using workspace" disabled, then during SCM polling the environment variables are not evaluated correctly when evaluating ref-specs and branch-specs.

          As a result, credentials are loaded to the git client using the unparsed URL, while when the git client is actually being run it uses the correct URL and fails to load the credentials.
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Mark Waite made changes -
          Labels Original: configuration plugin New: configuration newbie-friendly plugin
          Mark Waite made changes -
          Labels Original: configuration newbie-friendly plugin New: configuration plugin

            Unassigned Unassigned
            guss77 Oded Arbel
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: