This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-25
Channels
- # admin-announcements (2)
- # beginners (36)
- # boot (37)
- # cider (65)
- # cljsrn (92)
- # clojars (3)
- # clojure (225)
- # clojure-austin (5)
- # clojure-belgium (2)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-greece (2)
- # clojure-mexico (3)
- # clojure-news (2)
- # clojure-quebec (1)
- # clojure-russia (14)
- # clojure-spec (24)
- # clojure-uk (53)
- # clojurescript (34)
- # cursive (14)
- # datascript (9)
- # datomic (4)
- # defnpodcast (8)
- # devcards (30)
- # dirac (7)
- # editors (7)
- # emacs (1)
- # figwheel (1)
- # hoplon (85)
- # immutant (2)
- # incanter (1)
- # luminus (5)
- # off-topic (41)
- # om (18)
- # onyx (11)
- # perun (2)
- # re-frame (11)
- # reagent (9)
- # ring (3)
- # spacemacs (2)
- # spirituality-ethics (1)
- # test-check (19)
- # testing (12)
- # untangled (14)
- # yada (9)
lmergen will do - we've used Snap CI, but their builds will often terminate early for no reason on our side, and they seem to refuse to fix it - "just run another one", not great for very large projects that take an hour to build
I emailed circle CI, which mentions scale in their website description but I don't see any explicit features like pick your EC2 type or something
yes, that's a common attitude. seems like these CI tools optimize for the 80% case, but that leaves us with a pretty annoying problem
anyway, i'm trying to figure something out that uses AWS lambda, or another way to parallelize
Everything optimizes for the 80% case I think, and eventually everything dips into the 20% cases of a domain
out of curiousity, what do your integration test times (i.e., git clone
and lein test
) look like ?
for us right now, one of our biggest projects is at +- 20 minutes, and it starts to become a problem when many people are working on that code -- for which the only solution would be 'throw money at travis'
I'd go with on-premises CI in this case, e.g. http://concourse.ci