Did you ever get a response to this problem? Or maybe found a workaround? We have a "Dual Jenkins" solution (master/slave) to help us handle upgrades and config changes to our jenkins instance(es) in a "safer" manner, but it relies on using JCLI as opposed to RESTful calls. This bug or shortcoming prevents us from starting to use the Dual Jenkins solution, and we *really* need the JCLI build command to retrieve default parameter values for all parameters not included as -p arguments!
- Re: [URGENT] Default job parameters are not used - Bug? Adam Aquilon
