-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: ansible-plugin, envinject-plugin
-
Labels:
-
Environment:Jenkins Version: 1.623
Ansible Plugin: 0.3.1
envinject: 1.91.4
mask-passwords: 2.7.4
OS:3.4.83-70.111.amzn1.x86_64
Ansible Version: 1.9.2
-
Similar Issues:
I am unable to pass in a masked password as a variable via --extra-vars. I have tried using the EnvInject plugin and the Masked Password plugin to create the variable PASSWORD.
I then pass it in via
--etxra-vars="my_password=${PASSWORD}"
When I debug the ansible playbook instead of my_password being the masked value it is "*******".
It looks like the plugin does not attempt to unmask the variable before passing it to the playbook.
Hello.
I was using a simple password parameter and referencing it in the inline inventory content and ran across this problem. I was able to solve this problem by updating envinject to latest 1.92.1
H
Code changed in jenkins
User: Jean-Christophe Sirot
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/ansible/AbstractAnsibleInvocation.java
src/main/java/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandBuilder.java
src/main/java/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandInvocation.java
src/main/java/org/jenkinsci/plugins/ansible/AnsiblePlaybookBuilder.java
src/main/java/org/jenkinsci/plugins/ansible/AnsiblePlaybookInvocation.java
src/main/java/org/jenkinsci/plugins/ansible/ExtraVar.java
src/main/java/org/jenkinsci/plugins/ansible/workflow/AnsiblePlaybookStep.java
src/main/resources/org/jenkinsci/plugins/ansible/AnsibleAdHocCommandBuilder/config.jelly
src/main/resources/org/jenkinsci/plugins/ansible/AnsiblePlaybookBuilder/config.jelly
src/main/resources/org/jenkinsci/plugins/ansible/workflow/AnsiblePlaybookStep/config.jelly
http://jenkins-ci.org/commit/ansible-plugin/b8fc86d508104d494abf99bff125492a193668e1
Log:
JENKINS-29863 Add dedicated support for extra variables in build widget and pipeline
Fixed in ansible-plugin 0.5
I came across the exact same issue, right at the same time. The only thing we had in common was the envinject pluging. I rolled it back to v1.90 and the problem is gone. That's a regression in that plugin, then.