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 🙂
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)
The latest one I built runs at around 1 minute. The latest run was 1 minute and 1 second. 😊🎉
All it does is:
Nothing fancy. 🙃
How about tests?
Also, problems with the build are caught early because of a precommit script.
Part of the build.
about 30 seconds for a full deploy
I use Netlify and my site isn't that huge :)
Around 9 minutes.
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:
I used to work somewhere that for each PR we had to run 20 or more LXC containers each churning at a queue of 18k+ tests. It would take anywhere from 30 minutes to an hour depending on how badly developers had messed things up. There were no compilers involved, it was all pure python.
That's a painful amount of time. Did it improve at all?
Nope. It only got worse and worse. No one wanted to remove tests because no one wanted to be on the hook when the product broke. It was easier to burn money than get people to fix the tests.
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.
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.
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. :-)
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 👍
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.
(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 :)
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.
Noob here. Does CI mean 'continuous integration'?
~2 - 5 minutes. .net framework build, publish & octopus deploy
PHP app: 21 minutes run 100s of acceptance tests against a slim database
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.
around 20-25 minutes. It's a C# + TS project and it's quite big
C++/Qt: 45 minutes for release, 2 hours for tests
PHP: 5 minutes for release and tests
Ruby: 14 minutes
Go: 1 minute
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.