Try to retrieve dynamic axis value from Jenkins global properties straight away

[poolik]

This makes sure that if the dynamic value comes from Jenkins global variable then the matrix job will have active configurations correctly set / shown right away. Otherwise before the build has run (or after a restart) the active configurations of the matrix job won't reflect the dynamic axis values as they are only computed during the first build.

Potentially could expand this to try to load the value from System.getenv() as well.

[poolik]

@oleg-nenashev perhaps you could take a look and provide feedback or merge?

[poolik]

@oleg-nenashev a gentle reminder of this open pull request, hopefully you can find the time to review.

[oleg-nenashev]

Hmm, thanks for the ping.
I didn't even remember I'm somehow involved into this plugin.
Likely I've requested ownership at some point

[oleg-nenashev]

I'd say it's rather an architecture bug in the plugin.
The field must be always calculated dynamically on the build startup && it should not be persisted in builds since parallel runs are going to bork the build process (IIRC it is known issue). There is also no guarantee that the global variable variable won't be misused in such case.

A proper fix would be to add dynamic calculation of the layout for UI. Otherwise your project may display outdated value if somebody sets a global variable, then configures the job and modifies the property again.