-
Bug
-
Resolution: Unresolved
-
Minor
-
None
I have a parametrized job where the parameter value is being replaced as expected in the git Repository URL field. However if I use the same variable in the Repository browser URL, the parameter is not expanded on the https://my-jenkins-server/job/my-job/job-num/ pages build info pages.
On that page, the repository links are showing up as "https://my-git-server/${REPO}" instead of have "${REPO}" replaced with the parameter passed to the job.
The job is using the correct repo otherwise, so does look like the ${REPO} replacement is working for the Repository URL field.
I'm using the gitlab version 6.8 as the repository browser.
- is related to
-
JENKINS-30287 Environment variables are not expanded in tag names when publishing
-
- Open
-
-
JENKINS-17899 Add support for Token Macro expansion to GIT plugin
-
- Open
-
-
JENKINS-18005 Git Publisher plugin does not use token macro expressions for tag name
-
- Open
-
Unfortunately I have also fallen foul of this issue. I think my situation is the same as pwan describes in that I have a parametrized job where I pass in the name of the Git repository as the GIT_REPO parameter, the Git Repository Url is git@<MyGitServer>:/opt/git/$GIT_REPO and the job successfully expands the value of the Git Url and checks out the correct repository.
Using gitweb as the repository browser I want to pass the same parameter into the URL e.g. http://<MyGitServer>/gitweb/?p=$GIT_REPO. However GIT_REPO does not get expanded.
markewaite - I'm not sure which case you are referring to, I don't see how any replacement is needed, surely expansion is what we need?