++ Continuous Integration

do it yourself

do it now.

What CI means.

Why it is important.

How to make it happen.

Why you should trust me...

Michelle Krejci

Engineer

Find Craychee on Drupal.org

Twitter: @dev_meshev

Who are you?

a.) "I have heard the phrase 'continuous integration' but haven't decided if I should care."

b.) "I am sold on CI and want to know where to start."

c.) "My CI set up is pretty sweet and I want to feel smug about how much better I am doing it."

d.) "I have no idea what we are talking about."

back to that continuous...

what?

CI is often portrayed in terms of:

Or

Or

When I first started

trying to do CI

I started by

collecting CI tools.

Do not do this.

We were all trying to solve the same problem.

But

Continuous Integration.

is not primarily about cool toys.

continuous integration means...

Finding opportunities to

inject

small bits of

Quality Assurance

into the development process

at

every

That's it.

LMGTFY

Continuous integration is a process.

Wait. What exactly is it again?

What is CI?

• Revision Control
• Build Automation
• Automate Deployment
• Self-Testing Build
• Testing in a Clone of Production
• Frequent Commits
• Code Consolidation
• Fast Builds
• Build Availability
• Test Result Availability

Again!

If you have questions...

Remember to Tweet!

#DIYciQA

We will pick several for the end of the show.

Revision Control

Courtesy of Joefleming.net

• Version Branching should be minimized.
• Allows your developers to integrate their code easily.
• This is the base of what Continuous Integration is built around.

Build Automation

• A single command should have the capability of building a system.
• Should be buildable from a fresh checkout.
• Allows rapid development with a fast repeatable automated process.

Automate Deployment

• Build an environment on a trigger.
• Automated process is faster than manual.
• Less mistakes, always the same.
• Usually provides an automated contingency plan if it fails.

Jenkins

Self-testing Build

• When a build is created, tests should run to confirm that it behaves the way developers expect it to.

PHPUnit

• Popular unit testing software.
• Allows functional and other types of testing.
• Can be used with other software like Selenium or curl to facilitate other testing.

Testing in a Clone of Production

• Environmental changes can lead to failures.
• If a copy cannot be provided, a scalable version reduces risk.
• Use configuration management tools to configure all builds.

Chef

• One thing that makes Vagrant configurable.
• Allows version controlled configuration!
• Use to build like environments and quickly discern differences

Frequent Commits

• Makes debugging easier.
• Better history.
• Easier to merge, move, add, and remove changes.
• Makes Code Consolidation easier.

Code Consolidation

• Every user should commit to a baseline once a day.
• Helps tests catch problems early.
• Less problems merging code.
• Developers should expect broken features. (process can manage this)

Fast Builds

• Developers shouldn't be kept waiting.
• Resources on automatic builds shouldn't be kept waiting.

Build Availability

• It is more time effective to have environments prebuilt and "checked out" than building on the fly.
• Builds available for Stakeholders is a must.
• Everyone should be able to access/use the latest build.

Test Result Availability

• Confidence in product.
• Provides a "Warranty".
• Developers can find problems earlier.