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

Parameters not expanded in the Repository browser URL field

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • 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.

          [JENKINS-29842] Parameters not expanded in the Repository browser URL field

          pwan created issue -
          pwan made changes -
          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.

          pwan made changes -
          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

          pwan made changes -
          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

          pwan made changes -
          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

          pwan made changes -
          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.

          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164919 ] New: JNJira + In-Review [ 181743 ]
          Michael Fowler made changes -
          Link New: This issue is related to JENKINS-17899 [ JENKINS-17899 ]
          Michael Fowler made changes -
          Link New: This issue is related to JENKINS-30287 [ JENKINS-30287 ]
          Michael Fowler made changes -
          Link New: This issue is related to JENKINS-18005 [ JENKINS-18005 ]
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]

            Unassigned Unassigned
            pwan pwan
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: