[ 
https://issues.jenkins-ci.org/browse/JENKINS-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160212#comment-160212
 ] 

bogdaniosif commented on JENKINS-10899:
---------------------------------------

@gbois can you please comment on this feature request? I would like to make 
sure that it's clearly formulated since I see that it's the single remaining 
open issue for envinject.

I'll state again the need, as succinctly as I can:

    - Define in a single .properties file, env vars to be set by envinject 
during normal job execution for multiple jobs. Assume we need to store this 
file on the build server because it stores env vars needed before source 
control is accessed.

    - PROBLEM: The only way for a build engineer inspecting these jobs' 
configurations in Jenkins' web UI, to also inspect the content of the 
.properties file is to use an additional channel; e.g. connect remotely to 
Jenkins' host and list / edit that .properties file.

It would be of great help to at least be able to see the content of the 
.properties file via Jenkins' web UI, in read only mode. It would be fantastic 
to be able to edit the file via the Jenkins UI.
                
> Add the ability to show/edit from a job's configuration UI, a properties file 
> containing env vars to be set by envinject
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-10899
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10899
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: envinject
>            Reporter: bogdaniosif
>            Assignee: gbois
>
> When env vars to be set by envinject are stored in a properties file, the 
> following problem arises from a job's admin perspective: How is the file 
> viewed/edited? The problem is bigger when the file is not coming from SCM, 
> instead it just sits permanently in some location on the build server, e.g. 
> in the same folder as the job's config.xml
> _*Feature Request:*_ Add to envinject the ability to show/edit in the job's 
> configuration UI the content of a file containing env vars to be set. If it's 
> possible, show/edit the content inline in the configuration page.

--
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

        

Reply via email to