@Rui Mendes and Team,

Could you please help us for above issue?

Thanks,

Prabhu K

Hello,

The Pipeline Parameters values are passed into the Trigger Manifest in JSON format.

The only parameters sent to Jenkins are the Trigger Manifest and eventually the TriggeredBy. 

Cheers,
Duarte Castaño

Hello Duarte,

Thanks for the reply,

You mean to say we can't pass parameter value without Json format? and only one parameter we can pass i.e Triggered By?

But we have option to add multiple parameters on Trigger Pipeline from LT, as mentioned below, and i hope here values are not required on JSON format.

And please check below attached snapshot of Trigger Pipeline site properties configuration, we have configured required things for running pipeline and suggest us if anything we need to add/change.

Could you please guide us and provide us any documentation which address our concern.

Regards,

Prabhu K

Hi Prabhu,

The functionality is the ability to add information via "parameters" for each pipeline.
Those are added to the TriggerManifest, which is passed as an input parameter to the Jenkins pipeline.

I recommend that you check, in Jenkins, for the TriggerManifest content to see if the parameter values are present. 

This functionality is currently undocumented, but we intend to add it at a later stage.

In addition, in a future release of this component, we may add the functionality you were expecting (i.e., pipeline parameters sent as input parameters to Jenkins). 

As per your site properties configuration, as you have the Feature_UseTriggerManifest and SendTriggeredByParameterInManifest set to True, your Jenkins pipeline should only expect one input parameter: the TriggerManifest.

Regards,
Duarte Castaño