How long does your CI take?

Comments

[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 🙂

[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)

[Meghan (she/her)]

about 30 seconds for a full deploy

[Ben Halpern]

[Meghan (she/her)]

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

[John Paul Ada]

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. 🙃

[Diego Toral]

How about tests?

[John Paul Ada]

Part of the build.

[Diego Toral]

Awesome!

[John Paul Ada]

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

[rhymes]

Around 9 minutes.

[Alex Rudenko]

~10 minutes

[David Ojeda]

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.

[Arnaud Morisset]

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. :-)

[Lennart]

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.

[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.