Jenkins 2.x Pipeline from SCM with Parameters

[jwil...@gmail.com]

I feel like I must be doing something wrong here, but I have a Pipeline job that is getting its definition from version control.  The Pipeline defines parameters that the user has to supply.  If I change the set of parameters I want the build to have, I seem to have to run a failed job first to get the Pipeline re-parsed and then I can see the new parameters I defined.  Is there a better way to let the Pipeline job know about new parameters without letting a job run with incorrect or missing parameters?

[Yanson]

Did you get anywhere with this? I have the exact same issue, and it also affects other properties such as triggers.