3 ms·

Thanks for the link! (founder of CircleCI here) Before Circle, I led multiple engineering teams, building multiple products from "nothing" to "shipping, and ma

by arohner 13y ago

Thanks for the link! (founder of CircleCI here) Before Circle, I led multiple engineering teams, building multiple products from "nothing" to "shipping, and making lots of money". I set up buildbot, hudson, bamboo, jenkins, and some other things I don't even remember the name of. I was always the build guy, I was always the one that said "yes, we will be testing, yes, the build will be green." Those were controversial statements back then. I've been there, done that, and I didn't want to set up Bamboo again. I didn't want to debug why the tests failed. That's why I built Circle. Our customers, most of whom switched from Jenkins, will tell you we are a steal. Maybe your project is still simple. Maybe your platform is fairly stable. But for most professional developers, keeping CI running and green is a challenge. Even at Circle, I spend more time than I'd like debugging the test suite. But we're fixing that. Every day is spent making devs lives easier. Jenkins costs you nothing per month, but your developers cost money, and Circle's hardware is faster than digital ocean, and the cost of keeping the build green on Circle is lower than the cost of keeping it green on Jenkins anywhere else. If you're running a startup, or a tech company, odds are very good that salary is the number one cost center. Optimizing your Digital Ocean bill is penny wise, pound foolish.

nahname 13y ago
>Maybe your project is still simple. It's moving past the simple app point that gets problematic on someone else's solution. I have dependencies on postgres, redis and elasticsearch within the application. I need a browser too run the feature tests. I need phantomjs to run the javascript suite. Is there any saas offer that covers these? >...keeping the build green on Circle is lower than the cost of keeping it green on Jenkins anywhere else Keeping the build green involves my team figuring out what we broke. Faster build times help, is that what you mean here? Don't even get me started on the stuff we are doing with deployment automation... Edit: I think it was too hostile initially, appologies
- arohner 13y ago
  > I need redis and elasticsearch installed to run my test suite. Will that run on CircleCI? What kind of browser support for my feature specs do you offer? Yes. Redis and Elasticsearch are already installed. firefox, chrome, phantomjs, casperjs are already installed. Build pipelines are coming. I guarantee you they'll look nothing like what is available on Jenkins. They might be more opinionated than you like, but for the people they do work for, they'll save a lot of time. > Keeping the build green involves my team figuring out what we broke. Faster build times help, is that what you mean here? That's part of it. The other part is that we are a high-touch CI service. This week, rubygems had tons of SSL problems. Debugging that, and bugging the #rubygems IRC guys was "outsourced" to me. Thousands of developers didn't have to individually debug sporadic rubygems failures because I was doing it for them. We see common bugs and test failures often enough that we have in-app warning messages that say "hey, it looks like your selenium tests are failing because firefox auto-updated on you. If you upgrade your selenium gem/jar, that will probably help". Those are things that won't get added to Jenkins.
  - nahname 13y ago
    That is good to hear. I have been happy to set this stuff up myself, but it sounds like you have a great, full featured product. The world can always use easier ways to do automated testing.

by arohner 13y ago

nahname 13y ago

>Maybe your project is still simple. It's moving past the simple app point that gets problematic on someone else's solution. I have dependencies on postgres, redis and elasticsearch within the application. I need a browser too run the feature tests. I need phantomjs to run the javascript suite. Is there any saas offer that covers these? >...keeping the build green on Circle is lower than the cost of keeping it green on Jenkins anywhere else Keeping the build green involves my team figuring out what we broke. Faster build times help, is that what you mean here? Don't even get me started on the stuff we are doing with deployment automation... Edit: I think it was too hostile initially, appologies

arohner 13y ago
> I need redis and elasticsearch installed to run my test suite. Will that run on CircleCI? What kind of browser support for my feature specs do you offer? Yes. Redis and Elasticsearch are already installed. firefox, chrome, phantomjs, casperjs are already installed. Build pipelines are coming. I guarantee you they'll look nothing like what is available on Jenkins. They might be more opinionated than you like, but for the people they do work for, they'll save a lot of time. > Keeping the build green involves my team figuring out what we broke. Faster build times help, is that what you mean here? That's part of it. The other part is that we are a high-touch CI service. This week, rubygems had tons of SSL problems. Debugging that, and bugging the #rubygems IRC guys was "outsourced" to me. Thousands of developers didn't have to individually debug sporadic rubygems failures because I was doing it for them. We see common bugs and test failures often enough that we have in-app warning messages that say "hey, it looks like your selenium tests are failing because firefox auto-updated on you. If you upgrade your selenium gem/jar, that will probably help". Those are things that won't get added to Jenkins.
- nahname 13y ago
  That is good to hear. I have been happy to set this stuff up myself, but it sounds like you have a great, full featured product. The world can always use easier ways to do automated testing.