Can anyone confirm if non-string typed parameters (for example: choice) can
be declared for Jenkins Pipeline strategy?

jenkins-sync-plugin issue 131
<https://github.com/openshift/jenkins-sync-plugin/issues/131> appears to
add support for them except there appears to be a bug due to a typo
*(ChoiceParameterDefintion
probably should be **ChoiceParameterDefinition)* and I can't really find
anyone talking about this.

Thanks!
-- 

[image: BandwidthMaroon.png]

Andy Feller  •  Sr DevOps Engineer

900 Main Campus Drive, Suite 500, Raleigh, NC 27606


e: [email protected]
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to