• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • envinject-plugin
    • None
    • RHEL 6.3, Jenkins 1.534, envInject 1.88

      The help section for "Properties File Path" states: Gives a file path of a properties file. The file format must be the standard Java property file format.

      I have a property file that is in the Java property file format (it was written out by the store method of java.util.Properties), but the #, !, =, : are left escaped when envinject places the variable in the jenkins job.

      The linked page for Java property file format gives an example of:
      website = http\://en.wikipedia.org/
      In the example above, website would be a key, and its corresponding value would be http://en.wikipedia.org/
      I used this example in a property file that envInject used to place variables into the job and the result is:
      website http\://en.wikipedia.org/

          [JENKINS-20334] envInject leaves in backslash for #, !, =, :

          Mike Remillard created issue -

          Hi,

          this is definitely a bug. We are having exactly the same problem.

          Although this issue is old it would be nice to know if there is an "official workaround".

          Thomas Froehlich added a comment - Hi, this is definitely a bug. We are having exactly the same problem. Although this issue is old it would be nice to know if there is an "official workaround".

          Hi,

          the request from Thomas i fully support.

          Currently we can not use the EnvInject Plugin within the Jenkins Job configuration reading URLs from property files) as we would like to use.
          As a workaround we could write a Grrovy Script, which does this and execute it as first build step, but this is cumbersome.

          Would be great, if this issue gets fixed.

          Regards
          Ralf

          Ralf Schmitt-Roquette added a comment - Hi, the request from Thomas i fully support. Currently we can not use the EnvInject Plugin within the Jenkins Job configuration reading URLs from property files) as we would like to use. As a workaround we could write a Grrovy Script, which does this and execute it as first build step, but this is cumbersome. Would be great, if this issue gets fixed. Regards Ralf
          Rahul Mahulkar made changes -
          Assignee Original: Gregory Boissinot [ gbois ] New: Rahul Mahulkar [ rahul_mahulkar ]
          Rahul Mahulkar made changes -
          Assignee Original: Rahul Mahulkar [ rahul_mahulkar ] New: Gregory Boissinot [ gbois ]
          Rahul Mahulkar made changes -
          Comment [ Hi,
          I am facing this issue with 1.92.1 version. below is my property file look like
          DotCoverConsoleRunner=C:\JetBrains.dotCover.CommandLineTools.2015.1.1\dotcover.exe

          and inject variable is
          C\:\\JetBrains.dotCover.CommandLineTools.2015.1.1\\dotcover.exe

          Can someone please help if I am setting it in incorrect manner or look into this issue?

          Thanks
          Regards,
          Rahul Mahulkar ]

          Hugh Hu added a comment -

          Hi,

          We have encounter the same issue. Will this be fixed?

          Regards,

          Hugh Hu added a comment - Hi, We have encounter the same issue. Will this be fixed? Regards,
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 151858 ] New: JNJira + In-Review [ 178088 ]

          Oleg Nenashev added a comment -

          It has been resolved in 1.93 as a part of the JENKINS-31573 fix

          Oleg Nenashev added a comment - It has been resolved in 1.93 as a part of the  JENKINS-31573  fix
          Oleg Nenashev made changes -
          Link New: This issue duplicates JENKINS-31573 [ JENKINS-31573 ]
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            gbois Gregory Boissinot
            remmy412 Mike Remillard
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: