OK, I found out what is causing the problem. In freestyle jobs the configurations are not updated automatically and the newly introduced path variable is undefined and therefore null}. As soon as the configuration is updated (it's enough to just press save without changes) the {{path variable is defined and everything works as expected.
I just took over this plugin and I do not know if this kind of problem could have been prevented somehow. Oleg NenashevJesse Glick maybe you can tell us more about this?
OK, I found out what is causing the problem. In freestyle jobs the configurations are not updated automatically and the newly introduced {{path}} variable is undefined and therefore {{null}}
. As soon as the configuration is updated (it's enough to just press save without changes) the {{path}} variable is defined and everything works as expected.
I just took over this plugin and I do not know if this kind of problem could have been prevented somehow. [~oleg_nenashev] [~jglick] maybe you can tell us more about this?
Jesse Glick it's more of a general question regarding Jenkins plugins. Is there any best practice to introduce new plugin configuration variables (with a default value) without needing to manually refresh freestyle job configurations?
I did the update to version 1.14 again and followed the hints given by Robin Jansohn. I saved the job, which used the plugin without any changes. Now the deploy worked again. Thanks for the help!
Is there any best practice to introduce new plugin configuration variables (with a default value) without needing to manually refresh freestyle job configurations?
Not sure I can follow. The introduced variable is a string and should be automatically serializable? Do you have an example where a new configuration option was introduced and did not require a manual refresh?