Fork me on GitHub
Alex Miller (Clojure team)18:05:27

@dnolen @mfikes I looked at the cljs testing stuff a bit. I think probably the easiest thing is if you could convert that travis build into a docker file, which I could then easily run in jira. the alternative is installing a bunch of stuff on the build box and there are a bunch of reasons why that's non-ideal.


Seems reasonable to me.


@alexmiller so the idea is here is just use JIRA support to apply the patch and run tests?

Alex Miller (Clojure team)18:05:14

maybe I misunderstand what you're looking for, so let's step back ...

Alex Miller (Clojure team)18:05:24

I thought you were looking for a way to automatically run all tests on commit


@alexmiller oh JIRA has a view for that?


or you just mean run in JIRA


and use the hook for GitHub - ok

Alex Miller (Clojure team)18:05:25

crap, I said jira before but I meant jenkins


I was pretty confused


cool, sounds reasonable to me

Alex Miller (Clojure team)18:05:15

so, is goal to run all tests with each commit or to have a place to test patches with feedback ?


the first thing is higher priority


then we know if something is actually releasable


the later thing would be icing if related

Alex Miller (Clojure team)18:05:52

ok, I think the latter would build on the former anyway

Alex Miller (Clojure team)18:05:23

well, docker-izing the test would be the best path imo as it clarifies the system install requirements


would it be easy to partition by runtime kinda like how the JVM version stuff works for Clojure?


Testing V8, Node, JSC seems like a good start - and of course we need Node.js

Oliver George23:05:58

Hi All, I'm seeing compiler errors on windows. Just wondering if that's interesting or known.

Oliver George23:05:04

I had the feeling there were Windows CI tests.

Oliver George23:05:01

If it's worth tracking down I'll do a minimal repro