Is '../projectA/master' configured to accept parameter PROP_VERIFY (In the job definition, not in the Jenkinsfile)? Else I guess due to SEC-170 fixes, the parameter is not propagetd to the environment. Actually that would be a chicken-and-egg type problem. You need to get and execute the current jenkinsfile to see, if the param is allowed, but the param should already be set. See https://jenkins.io/blog/2016/05/11/security-update/ for details.
The linked issue seem to be a slightly different problem. Björn Am Mittwoch, 22. Juni 2016 13:13:48 UTC+2 schrieb Sverre Moe: > > Have defined parameter for my pipeline projects in the main pipeline > script: > properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: > [[$class: 'BooleanParameterDefinition', defaultValue: false, description: > 'Description', name: 'PROP_VERIFY']]]]) > > After building the first time with this I get the option "Build with > Parameters". > > Doesn't matter how I start a new build. Either manually or in the script: > build job: '../projectA/master', parameters: [[$class: > 'BooleanParameterValue', name: 'PROP_VERIFY', value: true]] > The environment variable env.PROP_VERIFY is not available. It it always > null. > > After building I am checking the following URL and can se that the > parameter is set: > http://server.company.com:8080/job/projectA/job/master/70/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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c117a5ac-ab9b-4622-b825-8848c28bed62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
