Hi thanks for the feedback! The purpose of the article was to share our unique data and make some sense of CI/CD use cases. Do you have suggestions, what would be a interesting read for you and we will put it in our roudmap. Best
Hi, thanks for the feedback! Relating frameworks to builds times is an awesome idea! We will start working on it. Do you have any other suggestions to make more sense from our data?
Build time is not just compile time. My app is Ruby so deployment time is nearly nil, but we have a regression suite that takes inching past an whole hour, that we run before every merge, and consult in detail before prod releases.
I hope I am an outlier (admitting that regression testing should not take this long, as there are larger projects with much broader scope that get the job done in significantly less time than that), but without CI this strategy would have already failed a long time ago, and it has helped us immeasurably with onboarding new developers and keeping release quality high.
That's exactly what CI does. It saves me from doing it, and it can do so with concurrent workers (say, if I finish the next thing before the hour is up. Should I be running the two concurrent test suites on my local machine? Or holding them in a queue, manually...)
My build spins up a browser and does expensive feature testing in a browser window to prove that our Rails app and JS code play nice together. For a long time, this was working in a way where the browser would stay behind other windows and not get in my way. Then a Chrome upgrade came and now, at the start of every example, the window moves itself to on top of the other windows on the screen, and steals the focus.
I know you're going to tell me to file a bug somewhere, but I suspect this change was made on purpose for a good reason.
(Maybe you remember pop-unders?)
CI solves this problem for me, rigorously, and in a way that is unobtrusive and not brittle. If you're not using CI, you probably don't understand the idea that "all developers should be able to run the test suite, but none of them should have to do it." That's the big idea. CI helps our team to increase their velocity, and keep it up.
Hi! Thanks for the meaningful contribution to the conversation. I share your thoughts on CI. I think it's a irreplacable tool for mobile app developers that actually reduces the hassle and repetitve grunt work. That's why this article was published in the first place! Take care!
I'm not sure if their numbers are sound. For example they claim to be able to deduce hosting service market share from their build numbers, but considering GitLab has built-in CI/CD system and GitHub doesn't it would make sense to me that the numbers they see are not directly comparable.
Interesting numbers but no real value without more analysis IMO.
The term CI/CD suddenly appears everywhere. Can «continuous integration and continuous delivery» be shortened to CI&D or CIaD? Or how do you pronounce CI/CD?
29 comments
[ 2.9 ms ] story [ 81.1 ms ] threadI'm surprised they got to the front-page with this tripe?
I hope I am an outlier (admitting that regression testing should not take this long, as there are larger projects with much broader scope that get the job done in significantly less time than that), but without CI this strategy would have already failed a long time ago, and it has helped us immeasurably with onboarding new developers and keeping release quality high.
"Build" time is not compile time.
My build spins up a browser and does expensive feature testing in a browser window to prove that our Rails app and JS code play nice together. For a long time, this was working in a way where the browser would stay behind other windows and not get in my way. Then a Chrome upgrade came and now, at the start of every example, the window moves itself to on top of the other windows on the screen, and steals the focus.
I know you're going to tell me to file a bug somewhere, but I suspect this change was made on purpose for a good reason. (Maybe you remember pop-unders?)
CI solves this problem for me, rigorously, and in a way that is unobtrusive and not brittle. If you're not using CI, you probably don't understand the idea that "all developers should be able to run the test suite, but none of them should have to do it." That's the big idea. CI helps our team to increase their velocity, and keep it up.
Interesting numbers but no real value without more analysis IMO.
I’ve only ever heard it pronounced ‘see eye see dee’ which is pretty quick to say while still being intelligible.
https://news.ycombinator.com/item?id=17235661