We're seeing some strange behaviour where it seems like Powershell scripts 
executed by Ansible are having their variables written to the system as 
environment variables as opposed to temporary session variables. The same 
scripts run through Jenkins don't write to ENV, so it seems like Ansible is 
causing this behaviour.

Any ideas of what the cause/solution might be? We aren't explicitly 
creating Windows environment variables through Ansible.


- Alek

You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to