The document discusses continuous integration, which aims to improve software quality and reduce delivery time by implementing quality control throughout development rather than after completion. It does this through practices like version control, local sandboxes, automated testing across staged environments. Continuous integration provides benefits like more frequent commits with confidence, visibility, and faster feedback through automated bots that behave predictably and consistently by always testing, building, and deploying code. Jenkins is mentioned as an easy to use continuous integration server with a large community and plugins.

1. Continuous
integration
Robots takin’ care of bizness.

2. Continuous wha?
“Continuous integration aims to improve the quality
of software, and to reduce the time taken to deliver
it, by replacing the traditional practice of applying
quality control after completing all development.
”

3. Practices
Version control.
Local development sandboxes.
Automated testing.
Staged environments.
sandbox, testing, production.

4. Benefits
Commit more often.
Commit with confidence.
Visibility into project.
Faster feedback loops.

5. Automated bots
No humans!
Write once, run everywhere.
Always behaves the same.
Predictable.

6. When to run the bots
After each commit.
After each push.
On a schedule.
When you click a button.

7. Continuous Bots
Always testing.
Always building.
Always deploying.

8. Make a good build
Run tests
Run lint / code standards checks.
Build packages/assets/artifacts.
Deploy!

9. Jenkins
Easy to use CI server.
Awesome community.
Plugins for everything.
There are other tools, and they are good too.

10. DEMO!