You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkin...@googlegroups.com
Hi,
I'm working on a Jenkins plugin and I have a
need to make a new environment variable available to all jobs in Jenkins. Sort of like a Jenkins global environment variable, or maybe exactly like that. I'm not sure. I just need it to be available to any script.
I already capture the value for this environment variable in one of the entries of my plugin's config.jelly file so it would feel like double work for the admin to also have to set it under "Manage Jenkins>Configure System>Global properties"
Then, as a second step, and thinking of maybe exposing others in the future, how should I go about name-spacing these? Sort of the way there are the env, params, docker, currentBuild environment variables. What should I extend in order to have my own name-spaced env vars? e.g.: foo.MY_VAR_1, foo.MY_VAR_2
Can anyone point me in the
right direction?
Thank you,
Miguelángel Fernández M.
Life is what happens to you while you're busy making other plans.
--John Lennon.
Jesse Glick
unread,
Oct 11, 2017, 3:07:03 PM10/11/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Dev
On Wed, Oct 11, 2017 at 8:25 AM, Miguelangel Fernandez
<miguela...@gmail.com> wrote:
> I'm working on a Jenkins plugin and I have a need to make a new environment
> variable available to all jobs in Jenkins. Sort of like a Jenkins global
> environment variable, or maybe exactly like that. I'm not sure. I just need
> it to be available to any script.