-
Notifications
You must be signed in to change notification settings - Fork 8
Home
Welcome to the azure-jenkins2-2016 wiki!
How to work:
- Implementation should be generic enough that there's nothing specific to any agency
- Continuous testing, release, compliance
- Short, working iterations
- Test in consumer Azure, port to GC
The automation process goals described as:
This document describes the “How To’s” or “Step-by-Step” instructions that will be used by the Office of (Redacted) teams to create automated continuous integration and delivery for applications that are developed and deployed to different environments (Dev, Staging, and Production). This document is intended for developers, build managers and product owners who want to automate their build, deployment and testing processes or adopt continuous integration and delivery techniques.
should be reduced from a 88-page Word doc to an 8-page Markdown doc kept in version control.
Main points:
- Build Azure resources repeatably, e.g.: with Terraform or Azure Resource Manager (ARM)
- Use Chef for managing resources repeatably
- Demonstrate use of continuous compliance - only on the node side, since compliance against ARM would be moot as that build is someone else's problem.
Most of the software we must install for "The Scan" is new to me. There are Software-Install-Notes.