Continuous Delivery to Cloud Foundry Why your Junior Devs will love it!

Some Background... ▪ Professional developer since November 2016 ▪ No previous coding experience (past life was in the insurance industry) ▪ Completed an intensive 3 month coding bootcamp ▪ After about 2 weeks of onboarding, moved on a client project and was assigned features to work on

Question? How can you take a coding bootcamp grad and get them pushing to master on a client’s app with minimal supervision?

Concerns? Senior Dev: Junior Dev: - It takes too long to train new developers to do everything - I don’t know how to do everything… yet - They might break the app - I might break the app

Solution Cloud Foundry + Continuous Delivery!

Test first mentality

Cloud Foundry

● Simple to use cli - easy learn Why do we like it?

I don’t care how, just run my app $ cf push myapp

$ cf scale -i 100 myapp SH!T, it’s a hit - I need more horsepower

$ cf create-service... I need a DB and but don’t want to manage it

$ cf create-space... I want orgs and spaces so I can safely share a platform

Concourse CI Pipeline

I want to build Pipelines now! … jobs: - name: job-deploy-myapp plan: - {get: resource-myapp, trigger: true} - put: resource-deploy-myapp params: manifest: myapp/manifest.yml path: myapp

Concourse CI Pipeline

Continuous Delivery “A software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time.” --Wikipedia

Cloud Foundry + Concourse = :)

Tests - (no external dependencies)

Deploy to Pre-production environment

End to end tests

Deploy to Production Environment

Tests on Production

What do your Jr Devs Learn from this?

Tests are important

Environment matters

The value of a short feedback loop

Why do we love it? ▪ Quick to get started ▪ Feel productive immediately ▪ Rapid learning due to frequent iteration

Thanks