DEV Community

Jess Lee
Jess Lee

Posted on

How long does your CI take?

Discussion (30)

Collapse
ben profile image
Ben Halpern

As someone who hasn't worked much in compiled language, tests and CI are my version of this

I usually come here when the CI is running ๐Ÿ™‚

Collapse
dmfay profile image
Dian Fay

Legacy work project: 9 minutes (includes build, test, reporting, and building Docker images)

Newer work project: 3 minutes (same)

Main open source project: 5 minutes (three not-always-in-parallel builds against three versions of Node, each individual build < 2 minutes)

Collapse
johnpaulada profile image
John Paul Ada • Edited on

The latest one I built runs at around 1 minute. The latest run was 1 minute and 1 second. ๐Ÿ˜Š๐ŸŽ‰

All it does is:

  1. Install dependencies
  2. Build project
  3. Deploy

Nothing fancy. ๐Ÿ™ƒ

Collapse
diegotoral profile image
Diego Toral

How about tests?

Collapse
johnpaulada profile image
John Paul Ada

Part of the build.

Thread Thread
diegotoral profile image
Diego Toral

Awesome!

Collapse
johnpaulada profile image
John Paul Ada

Also, problems with the build are caught early because of a precommit script.

Collapse
nektro profile image
Meghan (she/her)

about 30 seconds for a full deploy

Collapse
ben profile image
Ben Halpern

Collapse
nektro profile image
Meghan (she/her)

I use Netlify and my site isn't that huge :)

Collapse
rhymes profile image
rhymes • Edited on

Around 9 minutes.

CI

Collapse
paveltrufi profile image
Pavel Razgovorov

For a complete build, we need to compile three different projects (sometimes only two, sometimes only three, but just in some cases), all of them with their tests. All of that takes about 20 mins D:

Collapse
orkon profile image
Alex Rudenko

~10 minutes

Collapse
notriddle profile image
Michael "notriddle" Howell

About half an hour. The unit tests are pretty good, but we also have thick Selenium tests to go with them because we don't want the product to break.

It can get worse when Travis CI has a long backlog (like today), but I think that's true for everybody.

Collapse
leightondarkins profile image
Leighton Darkins

I'm working on two projects at the moment.

One is a somewhat poorly assembled collection of Java and Scala (almost micro) services with a React frontend. That's averaging about 30 minutes from commit to production.

The other is a lightweight web app, Node backend with React up front. It's averaging about 2.5 minutes from commit to production.

The 30 minute build time for the first project is really just a result of poorly orchestrated dependencies. We're part of the way through strangling out a monolith so the services currently all have to deploy together for... reasons โ˜น๏ธ. Each service independently builds and verifies itself in around 5 minutes though, so one day soon we'll have super speedy CI ๐Ÿ‘

Collapse
lennartb profile image
Lennart • Edited on

Our actual team project (~8 projects/assemblies) takes around 5 minutes including tests and deployment. Quality analysis runs once a day and takes about 15 minutes. Our full application suite takes longer, especially the tests but I'm not really involved with that, I think it's about 30 minutes. The former runs on TFS on-prem CI, the latter is a legacy MS-Build setup with mostly custom scripts.

Collapse
david_ojeda profile image
David Ojeda • Edited on

We have a big Grails project and unit + integration tests take ~2:30 minutes.

A full blue-green deployment takes 20 minutes; 10 of those are just waiting to make sure the new environment is all good.

Collapse
arnaudmorisset profile image
Arnaud Morisset • Edited on

On my current work project (which is an elixir umbrella app), it takes 4m 38s with 10 test workflows (from docker/kubernetes build to rabbitmq tests to business unit tests).

We use CircleCI, performances are really good. :-)

Collapse
maestromac profile image
Mac Siri

That's a painful amount of time. Did it improve at all?

Collapse
pshchelo profile image
Pavlo Shchelokovskyy

(I am a contributor to the) OpenStack cloud platform - depending on component up to 2 hours for the longest jobs, those being mostly integrated upgrade tests - check out the live CI status at zuul.openstack.org :)

Collapse
michaelgv profile image
Mike

C++/Qt: 45 minutes for release, 2 hours for tests

PHP: 5 minutes for release and tests

Ruby: 14 minutes

Go: 1 minute

Collapse
thomasvjames profile image
Thomas James

~2 - 5 minutes. .net framework build, publish & octopus deploy

Collapse
dellward profile image
Dell Ward

Noob here. Does CI mean 'continuous integration'?

Collapse
sshkey profile image
Erik Beltran

exactly.

Collapse
marceloandrade profile image
Marcelo Andrade R.

PHP app: 21 minutes run 100s of acceptance tests against a slim database

Collapse
shell profile image
Vladimir Penkin

around 20-25 minutes. It's a C# + TS project and it's quite big

Collapse
slaffik profile image
Slava Abakumov • Edited on

8 minutes for full atomic deploy: build, git export, zip, upload to server 45 MB, unzip, run migrations (db and/or other related to files), clean 2 types of cache, reload webserver.

Collapse
valerauko profile image
Vale

Ruby on Rails with Vue. Builds are running in a flash, but lots of legacy code and request specs slow things down. It averages around 20min now.