Ansible plugin adding curly braces to choice paramters

Community
1

Hi all,

We upgraded our jenkins recently (form 2.448 to 2.470). We have jobs that uses ansible-playbook step from ansible plugin. After upgrade we noticed that the choice parameters are added in curly braces while passing in extraArgs. With String the values are passed correctly. Any idea?

Here is console output from freestyle job. Notice the string param and choice param passed in ansible playbook.

Started by user Omprakash Paliwal
Running as SYSTEM
Agent exp-tools-n70rw is provisioned from template exp-tools
[EnvInject] - Loading node environment variables.
Building remotely on exp-tools-n70rw (ansible-deployment agent java linux ansible-latest exp-tools agents ansible) in workspace /home/jenkins/agent/workspace/WorkInProgress/print_choice_param
[print_choice_param] $ ansible-playbook dummy.yaml -f 5 -e {"choice1":false} -e string_param=some_string
/home/jenkins/.local/lib/python3.10/site-packages/paramiko/pkey.py:100: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.
  "cipher": algorithms.TripleDES,
/home/jenkins/.local/lib/python3.10/site-packages/paramiko/transport.py:259: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.Triple
2

See Add support for Boolean extra-var interpretation by Pexers · Pull Request #225 · jenkinsci/ansible-plugin · GitHub

This is the correct way to pass real boolean to ansible: Using Variables — Ansible Community Documentation

-e {"choice1":false}

Looks correct to me, it’s a false boolean