There are two ways to specify global environment variables. You can set them directly as name/value pair in the global settings, or let them import from a properties file.

If you need those variables in jobs run on slave nodes, you will notice that only those hard-coded variables are present. The loaded variables will not be available. Those are only available if the job is getting run on the master.

The workaround for now would be to load this properties file by specifying a build step in that job.