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

EnvInject refuses to set 2 variables with the same character sequence but different case (example no_proxy and NO_PROXY)

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

      I have tried this both using the key/value in the GUI and inside of a properties file.

      set no_proxy key and value
      set NO_PROXY key and value

      If the character sequence is the same aside from the case, the second variable will not be set. This is verified by looking in config.xml and returning back to the manage system page in the GUI and the second variable is not added. I think this is a bug since the shell allows you to do this and in the case of the HTTP_PROXY/http_proxy set of variables some applications look for uppercase while others look for lowercase so the plugin should allow you to do this as well.

          [JENKINS-31243] EnvInject refuses to set 2 variables with the same character sequence but different case (example no_proxy and NO_PROXY)

          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
            kmusard Kris Musard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: