-
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
-
[JENKINS-29842] Parameters not expanded in the Repository browser URL field
Description |
Original:
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. |
New:
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. |
Description |
Original:
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. |
New:
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 |
Description |
Original:
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 |
New:
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 repository setting |
Description |
Original:
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 repository setting |
New:
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 |
Description |
Original:
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 |
New:
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. |
I'm not sure what you're expecting parameter expansion to do in that case.
Should it be replaced with the default value (as is done for polling with a parameterized repository name)?
Should it be replaced with the value used in the last job?
Should it be replaced with the value used in the last successful job?