-
New Feature
-
Resolution: Unresolved
-
Trivial
-
None
-
Hudson 1.344, Java 1.5
It would be extremely usefull to move global variables that can be specified in Hudson's Configuration, to a new specific section called "Global Environment Variables".
I'm using global environment variables in hudson, that are used in all job's, instead of specifying them in each an every job. But I find it awkard to find them mixed with Hudson's other configurations, specially when they become too many.
Having their's own separated section would prove to be more logical when (ab)using them.
Thanks in advance.
- is related to
-
JENKINS-14538 Separate "configure tools" page
-
- Resolved
-
[JENKINS-5564] Relocate Global Environment variables to a new section
Description |
Original:
It would be extremely usefull to move global variables that can be specified in Hudson's Configuration, to a new specific section called "Global Environment" variables. I'm using global environment variables in hudson, that are used in all job's, instead of specifying them in each an every job. But I find it awkard to find them mixed with Hudson's other configurations, specially when they become too many. Having their's own separated section would prove to be more logical when (ab)using them. :-) Thanks in advance. |
New:
It would be extremely usefull to move global variables that can be specified in Hudson's Configuration, to a new specific section called "Global Environment Variables". I'm using global environment variables in hudson, that are used in all job's, instead of specifying them in each an every job. But I find it awkard to find them mixed with Hudson's other configurations, specially when they become too many. Having their's own separated section would prove to be more logical when (ab)using them. :-) Thanks in advance. |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 135656 ] | New: JNJira + In-Review [ 174359 ] |