Feb 22, 2017 - Rebecca Dodd  

Continuous Integration – a tool developers expect

77% of developers say Continuous Integration is integral to their everyday work – we break down what that means.

Watch our Continuous Everything webcast!

Continuous Integration – the practice that developers use to detect, locate and fix errors quickly by integrating their code frequently into a shared repository – is becoming a non-negotiable aspect of everyday work.

Continuous Integration (CI) automates testing of new code, sparing developers the time-consuming task of checking it manually, and with increasing numbers of companies using this approach every day, CI is essential to staying competitive and to retaining your talent.

Our Global Developer Report was launched last year to explore the ways in which developers work is changing, and how you as a business can adapt to get the best out of your development team. With a developer-heavy sample (more than half of respondents identify as developer or engineer), the survey revealed some truths about what matters to developers, how they choose to work and what tools they choose to do it with. To see what our research revealed, you can download the full report to learn more about what today’s developers want.

One of the key takeaways from the survey is that Continuous Integration now plays a crucial part in daily work, and is becoming more and more important to delivering great features frequently. CI frees up time that would otherwise be spent on finding and fixing errors, and it decreases the chance of shipping code that isn’t ready.

How much Continuous Integration is used

CI Is Used by More Than Half of Developers

And those developers are using it more than 75 percent of the time. More than 20 percent use it nearly 100 percent of the time, with only 4 percent not using CI at all. The trend is clear: CI is becoming increasingly important.

CI Makes Best Use of Your Team’s Time

Deploying untested code means time is wasted on backtracking to find and fix bugs. Nearly 54 percent of our respondents work on a developer team of fewer than 10, so any resources spent on tasks that could be automated has a huge impact. Adopting CI means new code is automatically tested for errors, so your developers spend less time on dull, manual testing and can focus on the work that inspires them – like building great new features.

77 Percent of Developers Think CI Is Essential

They rated it as very or extremely important to their everyday work. If this trend is to continue, CI will soon be an essential element of your software development lifecycle, and companies that are resistant to adopting it may find their development team growing restless: 36 percent of developers said they would turn down a job if the company did not use the latest tools.

Continuous Methods Aren’t Just for Developers

We’ve come a long way since a release consisted of distributing CDs to retailers, and it’s not just developers who are changing their methods. The practice of working continuously – releasing in small, manageable iterations often and integrating feedback and changes frequently – is something everyone in a company can adopt, to work more efficiently and collaboratively. In our upcoming webcast, we’ll explore in more detail how the continuous approach can help you deliver customer value at the pace it takes to complete.

Watch our webcast      From Continuous Integration to Continuous Everything      on March 1st. Register here!

Tweet us @GitLab, check out our job openings, or add your questions and suggestions to our issue tracker!

For the latest and most detailed news follow @gitlab on Twitter. Future blog posts suggestions RSS

Install GitLab in 2 minutes

With Ubuntu, Debian, CentOS and Raspbian packages or from source

Install GitLab Now

Try GitLab Enterprise Edition risk-free for 30 days.

No credit card required. Have questions? Contact us.