part 1 Continuous delivery/ Continuous integration

CD: practice  of creating repeatable, reliable process for releasing software

CD : Release often, release faster , greater reliablility


- innovative,fast feedback,warranty
- faster bug discovery and fixes

Outcome
- unit and integration tests using Docker
- Build and testing docker release images
- push button style automation for continuous delivery and deployment
- Continuous delivery pipeline using Jenkins 2.0
- Setup a deployment pipeline that deploy applicatin to AWS
- Build production class continuous delivery workflow

CI/CD for ...
Operation guys:
build continuous delivery pipeline
automate test,build,release and deploy
Infrastructure as a Code

Architects:
application agonistic method(crossplatform/interoperability)
run on any CD system like jenkins
immutable infrastructure
Infrastructure as code

Developers:
wrap test and build actions
your application works any machine
run production like env locally
fast track your changes in production

CD Architecture and Workflow

1) Testing stage (unit and integration test)
    Use docker to wrap test runners

2) Build stage
    eg. python wheel, java jar files
    This must represent as tested application state
    create deployable artifact
    -- precompiled and pre built
    -- installation requires no development dependencies

3) Release Stage

    Build Docker Release image
    - Includes minimum runtime enviroment
    - install application artifacts
    Release Enviroment
    - Production like enviroment
    - Use external test runner to run acceptance test

    Tag and Publish
    - only if acceptance test pass
    - docker HUB