[
https://issues.jenkins-ci.org/browse/JENKINS-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162294#comment-162294
]
gbois commented on JENKINS-13552:
---------------------------------
With the EnvInject plugin, environment variables are injected at runtime.
Reporting environment variables are post build.
For matrix jobs, there is a dedicated report on each configuration and there is
not inheritance from the parent job.
Knowing if a environment variable has been injected as a pre build or as a
build step is not so important for me.
Could you give more use cases?
> Provide extended 'injected environment variables' view
> ------------------------------------------------------
>
> Key: JENKINS-13552
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13552
> Project: Jenkins
> Issue Type: New Feature
> Components: envinject
> Reporter: Marcel Huber
> Assignee: gbois
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
