-
Bug
-
Resolution: Unresolved
-
Minor
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
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. |
Workflow | Original: JNJira [ 164671 ] | New: JNJira + In-Review [ 181673 ] |
Summary | Original: Some environment variables are may not be expanded during git polling | New: Some environment variables are not expanded during git polling |
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. |
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. |
Assignee | Original: Nicolas De Loof [ ndeloof ] |
Labels | Original: configuration plugin | New: configuration newbie-friendly plugin |
I have a fix for this issue, which will be submitted shortly.