We do something similar when we merge code.  Spin up a VM and run the new 
code changes basically.  We just review the logs in jenkins (we use that as 
a frontend instead of Tower) and/or use the slack module to send ourselves 
any errors.

We took the painful step of going from 2.2 and 2.4 and found mostly our 
custom modules had to be modified.  We also moved away from any deprecated 
Ansible modules at the same time (include module, for example) and modified 
our code for future testing.



On Tuesday, February 6, 2018 at 3:06:57 AM UTC-5, Mike Fennemore wrote:
>
> Hi all,
>
> So I have been looking at moving to later versions of Ansible (currently 
> way back on 2.1.4). Ideally I want to have an automated(or relatively 
> automated)
> way to work through all the internal roles and playbooks against different 
> versions of Ansible.
> Does anyone currently have this kind of workflow? My initial thought was 
> to have a CI solution to spin up containers/vm's and have it do test runs 
> (Molecule/Test-kitchen)
> or alternatively have each version of Ansible run in check mode to check 
> for any possible issues.
> The other issue then becomes getting this information out to log 
> processing (logstash perhaps?)
>
> Looking forward to hearing back.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/35b26b7f-582a-4a33-8209-0cace6b84aa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to