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

Environment variables don't work in the CVS ROOT Field

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: cvs-plugin
    • Labels:
      None
    • Environment:
      Latest Jenkins and latest CVS plugin
    • Similar Issues:

      Description

      I set up a new environment variable(MYCVSROOT -> :pserver:myuser:mypassw@myhost:/mycvsrepo) on the configure system page.
      I created a new job and I wanted to use this environment variable(%MYCVSROOT% or $MYCVSROOT) in the Source Code Management/CVS Root field, but the value of the MYCVSROOT does not substitued.

        Attachments

          Activity

          Hide
          mc1arke Michael Clarke added a comment -

          Do environmental variables work in any of the fields for you? We don't currently parse them for the 'known hosts' and 'private key location' fields, but every other field should be parsed for environmental variables. It could be that we don't have a set of environmental variables at the time we do the parsing (although I don't know why this would be the case), but this would result in no fields being parsed so should be easy to check.

          Show
          mc1arke Michael Clarke added a comment - Do environmental variables work in any of the fields for you? We don't currently parse them for the 'known hosts' and 'private key location' fields, but every other field should be parsed for environmental variables. It could be that we don't have a set of environmental variables at the time we do the parsing (although I don't know why this would be the case), but this would result in no fields being parsed so should be easy to check.
          Hide
          babazs Torresz Daniel added a comment -

          Yes, in any another fileds the environment variables are work, but not in the cvs root field.

          Show
          babazs Torresz Daniel added a comment - Yes, in any another fileds the environment variables are work, but not in the cvs root field.
          Hide
          steverobertson_at_hotmail_dot_com steve robertson added a comment -

          I am having a similar issue, windows environment
          if I use $ e.g. $CVSBranchTag for branch name it substitutes but no matter what I do $CVSModuleName, %CVSModuleName% for the remote module name field it won't substitute.

          Show
          steverobertson_at_hotmail_dot_com steve robertson added a comment - I am having a similar issue, windows environment if I use $ e.g. $CVSBranchTag for branch name it substitutes but no matter what I do $CVSModuleName, %CVSModuleName% for the remote module name field it won't substitute.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: mc1arke
          Path:
          src/main/java/hudson/scm/AbstractCvs.java
          src/main/java/hudson/scm/CVSSCM.java
          src/main/java/hudson/scm/CvsProjectset.java
          http://jenkins-ci.org/commit/cvs-plugin/bfc1a2dd6034895a31267bfaf3275d59bae0b592
          Log:
          [FIXED JENKINS-13186] Perform environmental expansion on module name fields

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/AbstractCvs.java src/main/java/hudson/scm/CVSSCM.java src/main/java/hudson/scm/CvsProjectset.java http://jenkins-ci.org/commit/cvs-plugin/bfc1a2dd6034895a31267bfaf3275d59bae0b592 Log: [FIXED JENKINS-13186] Perform environmental expansion on module name fields

            People

            • Assignee:
              Unassigned
              Reporter:
              babazs Torresz Daniel
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: