-
Bug
-
Resolution: Unresolved
-
Major
-
None
To replicate:
1) create a job and pass in refspec as build parameter e.g. "$GIT_REFSPEC"
2) use the parameter "$GIT_REFSPEC" as the SCM configuration for git-plugin
3) The build will use the exact string "$GIT_REFSPEC" rather than the actual value of $GIT_REFSPEC for the fetch operation.
For example:
01:26:08 using GIT_SSH to set credentials Gerrit SSH Key
01:26:08 > /usr/bin/git fetch --no-tags --progress ssh://[github-project-url] $GIT_REFSPEC --depth=2
01:31:43 > /usr/bin/git config remote.origin.url ssh://[github-project-url] # timeout=10
01:31:43 > /usr/bin/git config --add remote.origin.fetch $GIT_REFSPEC # timeout=10
I believe the .toString in this line is causing this problem:
- is blocking
-
JENKINS-50131 git parameter
- Closed
- is duplicated by
-
JENKINS-49834 Variable at branch name do not eval
- Closed
- is related to
-
JENKINS-30287 Environment variables are not expanded in tag names when publishing
- Open
-
JENKINS-34603 git scm poll not working with global environment variable
- In Progress
-
JENKINS-23477 git plugin sparse checkout path field does not expand variables
- Fixed but Unreleased
-
JENKINS-42971 Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
- Resolved
-
JENKINS-63457 ENV VAR / Job Parameter not being used in Git Checkout
- Closed
-
JENKINS-49834 Variable at branch name do not eval
- Closed