Jenkins World 2017: Infrastructure Testing: Validating your Cloud Configuration in Jenkins Pipelines

Gone are the days of “stacking and racking" servers and networking gear. Infrastructure is software now and needs to be managed the same way we manage feature and testing code. But how do we take a test-driven approach to cloud resources? What constitutes success or failure, and how do we automate these infrastructure assertions like we do other kinds of tests?

Fugue is a cloud infrastructure management system designed to provision infrastructure and ensure it conforms to business rules, corporate IT policies, and known-good practices. Using a straightforward declarative syntax, teams can treat infrastructure code the same way they manage feature code and tests, and break the build if the infrastructure is wrong.

In this session, we will demonstrate:

*Declarative code for provisioning a complete application environment in AWS

*How to define a set of success conditions, including region-awareness, resource cost constraints, security group ingress rules, and other criteria

*Using a git flow model and Jenkins Pipeline to test different rules per branch

*Bringing it all together for on-demand policy-compliant production environment clones for every stage of delivery