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

On Friday, 23 September 2016 21:05:49 UTC+1, jwil...@gmail.com wrote:
>
> 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?
>

-- 
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/c87d15d4-1ec9-454f-8b7e-1a927b77b783%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to