Yes, basically you could retrieve the job XML parsing for the parameter definitions storing the default values and then changing the values you want. Your function could also stop if not all mandatory fields are set.
I wrote my own jenkins controller (cannot publish the moment) but that one is not bad: https://github.com/txels/autojenkins However one important feature is missing: https://github.com/txels/autojenkins/issues/30 (CSRF protection) Regards, Thomas On Monday, August 15, 2016 at 8:53:44 AM UTC+2, Daniel Olausson wrote: > > Hi, > > I have a job that I would like to trigger via REST where I have one > parameter that I want to change every time and the other ones I would like > to use the default values for. If I do a POST to /build it just ignores the > default values and set them to empty. If I do a post to > /buildWithParameters I can't set the new value for the parameter I want, > the default values for all parameters are taken. > > How can I achieve this? First do a GET to get the default values, and then > do a POST to /build with all the parameters even if they are just the > default? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/10497232-60ea-4f9a-be8a-77820a60e9bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
