@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?

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

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

@alexmiller oh JIRA has a view for that?

no

or you just mean run in JIRA

and use the hook for GitHub - ok

crap, I said jira before but I meant jenkins

haha

I was pretty confused

me too

and it was my fault :)

cool, sounds reasonable to me

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

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

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

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

Quick example here. https://gist.github.com/olivergeorge/4654a332cf45d438ee6009873a3fb2fe

I had the feeling there were Windows CI tests.

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