Demonstrating the pros and cons of using services to help replace/augment your existing build stack

1. Continuous Integration
As A Service
Frontier Lunch and Learn
February 22, 2017
Alex Meadows

2. 
Principal Consultant (Data and Analytics),
CSpring

Business Analytics Adjunct Professor, Wake
Tech

MS in Business Intelligence

Loves working in open source code

Passion in developing BI solutions that provide
end users easy access to necessary data to
find the answers they demand (even the ones
they don’t know yet!)
Twitter: @OpenDataAlex LinkedIn: alexmeadows
GitHub: OpenDataAlex Email: ameadows@cspring.com
About Alex

3. Agenda

What Is Continuous Integration?

Continuous Integration for Smaller Development Teams/Individuals

Q&A
Please feel free to ask questions throughout the presentation!

4. CI Life-cycle

5. Typical CI Stack

6. Typical CI Stack

7. Typical CI Stack

8. Typical CI Stack

9. Typical CI Stack

10. Typical CI Stack

11. Typical CI Stack
Deployed Software

12. Pros and Cons
● Fully configurable
● Customized to fit your
environment
– Virtual Machines
– Data store integration
● On-site build help
(see build master)
● Maintenance of
customized
environment
● Accessibility
● Potential single points
of failure (see build
stack, build master)
Typical CI Stack

13. Build Master
● Solution Architect
● Troubleshooter
● Administrator
● Magician
● Typically very, very
under-appreciated

14. What About Solo Devs/Small
Teams?
● Build Master role is either
ignored or as-needed
● Builds are when the group
can find time
● Documentation
missing/out of
date/rushed
● Testing may/may not exist

15. Services To The Rescue!
Deployed Software

16. Some Caveats
● Most services listed are free for open source
● Closed source ups the cost significantly for
some of these services
● New services are coming up regularly –
apologies if I missed your favorite!

17. Pros and Cons
● No hardware to maintain
● Simple configuration and
management
● Anyone can manage
scripts
● Very accessible
● Distributed build help
(yourself, team, or
services)
● Reliant on services
● Anyone can manage
scripts
● Security more of a
concern
Service CI Stack

18. Integration
● These tools are designed to play well with each other.
● Badges are your friend :)

19. GitHub/Travis Integration

22. From Travis To Coveralls

26. Twitter: @OpenDataAlex LinkedIn: alexmeadows
GitHub: OpenDataAlex Email: ameadows@cspring.com