1.
Continuous testing with
Molecule, Ansible, and
GitHub Actions
Jeff Geerling
(geerlingguy)

2.
The earlier you catch defects,
the cheaper they are to fix
David Farley
2

3.
Jeff Geerling (geerlingguy)
• Ansible user since 2012
• Wrote a book: Ansible for DevOps
• Writing another book: Ansible for Kubernetes
• OSS maintainer:
• 200+ projects
• 27,000 stars
• 14,000 forks
`whoami`
3

4.
4
Molecule and
GitHub Actions CI
The example used in this presentation is based on an
example in chapter 13 of Ansible for DevOps, which
you can get at www.ansiblefordevops.com

5.
(In Playbook directory)
1. Install Molecule:
pip3 install molecule[docker]
2. Create a default scenario:
molecule init scenario
3. Modify the scenario to run this playbook.
Set up Molecule
6

6.
molecule/default/molecule.yml

7.
molecule/default/converge.yml

8.
molecule/default/verify.yml

9.
11
GitHub Actions
Integration

10.
(In Playbook directory)
1. Create a GitHub 'workflows' directory:
mkdir -p .github/workflows
2.Create a CI workflow:
touch .github/workflows/ci.yml
Set up GitHub Actions
12

11.
15
Complete Example is
on GitHub
Also includes example of testing on two different operating systems:
https://github.com/geerlingguy/ansible-for-devops/tree/master/molecule

12.
It's impossible
to maintain many projects
without good CI
Jeff Geerling
16
#DevOpsHaiku

13.
Red Hat is the world’s leading provider of enterprise
open source software solutions. Award-winning
support, training, and consulting services make
Red Hat a trusted adviser to the Fortune 500.
Thank you
youtube.com/user/RedHatVideos linkedin.com/company/Red-Hat
facebook.com/ansibleautomation twitter.com/ansible