For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
dev.to staff -
dev.to staff -
Liubov Vas -
dev.to staff -
Top comments (28)
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?
Part of the build.
Awesome!
Also, problems with the build are caught early because of a precommit script.
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:
~10 minutes
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'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 👍
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.
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.
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. :-)
That's a painful amount of time. Did it improve at all?
(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 :)
C++/Qt: 45 minutes for release, 2 hours for tests
PHP: 5 minutes for release and tests
Ruby: 14 minutes
Go: 1 minute