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

Properties File Path handles ${VARIABLES} in filename inconsistently

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • envinject-plugin
    • None

      Moved from https://github.com/jenkinsci/envinject-plugin/issues/23

       

      I want to load a properties file such as /opt/jenkins/${GIT_COMMIT}.properties.

If I define Properties File Path in "Prepare an environment for the run" then it is interpreted as a literal (which is unhelpful); however Properties File Path in "Inject environment variables" (i.e. as a build step) is interpreted correctly (i.e. the filename is dynamic).

Loading the properties file as a build step is a partial workaround, except that options such as "Load script and properties files from the master" are not presented at this stage.

It would be helpful if both "Properties File Path" fields interpreted variables in the filename.

      Full discussion is attached as PDF

        1. fullIssue.pdf
          274 kB

          [JENKINS-44977] Properties File Path handles ${VARIABLES} in filename inconsistently

          Oleg Nenashev added a comment -

          Unfortunately I will not have time to work on EnvInject issues for a while. I decided to unassign all issues so that somebody can take them and finalize.

          Context: The plugin has been waiting for adoption for ~2 years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance

          Oleg Nenashev added a comment - Unfortunately I will not have time to work on EnvInject issues for a while. I decided to unassign all issues so that somebody can take them and finalize. Context: The plugin has been waiting for adoption for ~2 years. During all this time I was trying to keep this plugin afloat by reviewing the incoming pull requests, fixing defects and keeping the codebase up to date to simplify the handover. But I have not been using this plugin on my own so that such maintenance was a bit lame. I invite all active users to contribute to the plugin by taking ownership of this plugin and of EnvInject API. I am happy to provide any required knowledge transfers and do some assistance during the first months of maintenance

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: