5 Signs You Need Continuous Integration
Upcoming SlideShare
Loading in...5
×
 

5 Signs You Need Continuous Integration

on

  • 2,515 views

Before the days of Continuous Integration (CI), the development process for web applications took long. They were coded, launched and then tested. As a result, new features weren’t being released as ...

Before the days of Continuous Integration (CI), the development process for web applications took long. They were coded, launched and then tested. As a result, new features weren’t being released as quickly.

CI helps bring together the separate components the development team is working on into one place where developers can spend less time on debugging and more time on building new features. Find out if you need CI for your next web development project in this SlideShare.

Get more on web development, design and strategy on our blog: http://blog.thelevel.com.

Statistics

Views

Total Views
2,515
Views on SlideShare
1,953
Embed Views
562

Actions

Likes
3
Downloads
8
Comments
0

6 Embeds 562

http://agilewebstrategy.org 267
http://blog.thelevel.com 231
https://twitter.com 47
http://localhost 13
http://agilewebstrategy.wordpress.com 3
http://1k-subscribe-email.ajones-thelevel.appspot.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

5 Signs You Need Continuous Integration 5 Signs You Need Continuous Integration Presentation Transcript

  • 5 Signs You Need CONTINUOUS INTEGRATION How CI Revolutionized the Web Development World www.thelevel.com
  • A long, long time ago (well, not that long ago) when web applications were developed, they were coded, launched and then tested (in that order).
  • Testing was a tedious process since developers would click around the application to find bugs.
  • The man hours spent on this was long and expensive. As a result, new features being added to web applications took longer than it needed to be.
  • And then, Continuous Integration came along.
  • Continuous Integration or CI is cohesive approach to web application and software development. It is the process where developers deploy, integrate and test their code many times a day to a shared repository in smaller iterations as opposed to big chunks.
  • So, how do you know if you need Continuous Integration?
  • #1 There’s a team of developers working on separate components of your web application. And each developer is storing his/her code on their own machines.
  • One of the core principles of CI is to maintain a single source repository.
  • Developers commit their code several times a day to the shared repository where it is automatically tested.
  • This brings together the separate components the development team is working on in one place. By having the build tested automatically, developers can spend less time debugging and more time focused on building new features.
  • Software bugs cost the US economy $59.6 billion annually. RTI International: The Economic Impacts of Inadequate Infrastructure for Software Testing
  • #2 You believe in automation.
  • Builds can automatically be built with a single line of code. This is a powerful feature of CI which allows companies to automatically deploy applications.
  • Automated Deployment combined with Build Automation allows companies to save development time since developers can deploy much faster (in a matter of seconds as opposed to minutes and hours!).
  • #3 Your development team is spending a big chunk of time debugging.
  • CI runs tests regularly instead of postdeployment or in the production environment. Whenever code is committed to the system, a build is created. Developers are notified to check the quality of their code if the test returns with an error.
  • CI will help you reduce your overhead costs of development by finding bugs during the development stage.
  • #4 Releases are slower since QA has to wait for the actual deployment to happen.
  • QA teams no longer have to wait until new features are deployed.
  • CI is an excellent quality control system since testing is done during the developmen phases as well as post-deployment.
  • #5 You want to gain visibility on your project.
  • CI helps companies see trends and manage code quality throughout their development.
  • CI encourages your development team to generate API-like documentation for all the code committed by developers. It also provides real-time information on the code quality.
  • CI ensures higher code quality, quicker releases and an overall better end product.
  • And so with CI, the web development community rejoices!
  • Who are we? The Level specializes in developing custom websites and web applications. We build custom web experiences that connect, engage and inspire for global and soon-to-be global brands. Get more on web development, design and strategy on our blog HERE.
  • Do you want to create b e t t e r web applications?
  • Let’s Connect www.thelevel.com The Level on LinkedIn @levelCMS
  • Credits Images www.gratisography.com www.morguefile.com/ www.openhatch.org/ Flickr: Kenny Louie www.thelevel.com