Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Continuous Integration
As A Service
Frontier Lunch and Learn
February 22, 2017
Alex Meadows

Principal Consultant (Data and Analytics),
CSpring

Business Analytics Adjunct Professor, Wake
Tech

MS in Business In...
Agenda

What Is Continuous Integration?

Continuous Integration for Smaller Development Teams/Individuals

Q&A
Please f...
CI Life-cycle
Typical CI Stack
Typical CI Stack
Typical CI Stack
Typical CI Stack
Typical CI Stack
Typical CI Stack
Typical CI Stack
Deployed Software
Pros and Cons
● Fully configurable
● Customized to fit your
environment
– Virtual Machines
– Data store integration
● On-s...
Build Master
● Solution Architect
● Troubleshooter
● Administrator
● Magician
● Typically very, very
under-appreciated
What About Solo Devs/Small
Teams?
● Build Master role is either
ignored or as-needed
● Builds are when the group
can find ...
Services To The Rescue!
Deployed Software
Some Caveats
● Most services listed are free for open source
● Closed source ups the cost significantly for
some of these ...
Pros and Cons
● No hardware to maintain
● Simple configuration and
management
● Anyone can manage
scripts
● Very accessibl...
Integration
● These tools are designed to play well with each other.
● Badges are your friend :)
GitHub/Travis Integration
From Travis To Coveralls
Twitter: @OpenDataAlex LinkedIn: alexmeadows
GitHub: OpenDataAlex Email: ameadows@cspring.com
Continuous Integration As A Service
Continuous Integration As A Service
Continuous Integration As A Service
Continuous Integration As A Service
Continuous Integration As A Service
Nächste SlideShare
Wird geladen in …5
×

Continuous Integration As A Service

113 Aufrufe

Veröffentlicht am

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

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Continuous Integration As A Service

  1. 1. Continuous Integration As A Service Frontier Lunch and Learn February 22, 2017 Alex Meadows
  2. 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. 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. 4. CI Life-cycle
  5. 5. Typical CI Stack
  6. 6. Typical CI Stack
  7. 7. Typical CI Stack
  8. 8. Typical CI Stack
  9. 9. Typical CI Stack
  10. 10. Typical CI Stack
  11. 11. Typical CI Stack Deployed Software
  12. 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. 13. Build Master ● Solution Architect ● Troubleshooter ● Administrator ● Magician ● Typically very, very under-appreciated
  14. 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. 15. Services To The Rescue! Deployed Software
  16. 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. 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. 18. Integration ● These tools are designed to play well with each other. ● Badges are your friend :)
  19. 19. GitHub/Travis Integration
  20. 20. From Travis To Coveralls
  21. 21. Twitter: @OpenDataAlex LinkedIn: alexmeadows GitHub: OpenDataAlex Email: ameadows@cspring.com

×