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

Provide extended 'injected environment variables' view

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • envinject-plugin
    • None

      Especially in multi configuration jobs and master/slave environments, it is sometimes difficult to examine where an injected value comes from and probably why it is different to our expectation.

      I guess a UI containing an env location matrix would help to figure out the origin of a value.

      Example:

      Variable name injected value injected from masters value propertiesfile value slave value groovy script ...
      HOME /var/lib/jenins slave /home/jenkins – /var/lib/jenkins – ...
      ...              

      I could also think of such a matrix as a help for configuration when you don't actually know all parties potentially injecting values for a variable.

          [JENKINS-13552] Provide extended 'injected environment variables' view

          Marcel Huber created issue -
          Marcel Huber made changes -
          Summary Original: Provide extended 'injected environment variables' New: Provide extended 'injected environment variables' view
          Gregory Boissinot made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 144018 ] New: JNJira + In-Review [ 185408 ]

            gbois Gregory Boissinot
            marcelhuber Marcel Huber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: