Continuous integration has been adopted in the software-development world for a while, but it is relatively new to network engineering. We are admittedly a bit behind in terms of using continuous integration in our network infrastructure. It is no doubt a bit of a challenge to think of our network in terms of code when we are still struggling to figure out how to stop using the CLI to manage our devices.
There are a number of good examples of using Jenkins for network automation. One is by Tim Fairweather and Shea Stewart at AnsibleFest 2017 network track: https://www.ansible.com/ansible-for-networks-beyond-static-config-templates. Another use case was shared by Carlos Vicente from Dyn at NANOG 63: https://www.nanog.org/sites/default/files/monday_general_autobuild_vicente_63.28.pdf.
Even though continuous integration might be an advanced...
