De la guardo setup clojure 34

[seancorfield]

Update CLI to 1.10.3.1029 for CI and manually install tools.tools so clojure -Ttools works.

This is a workaround for DeLaGuardo/setup-clojure#34

[seancorfield]

Ugh! I should have rebased that against master after updating it. I guess you can squash it to a single commit in the PR?

[coveralls]

Pull Request Test Coverage Report for Build 1481414130

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.8%) to 50.973%

---

Totals
Change from base Build 1478823455:	0.8%
Covered Lines:	131
Relevant Lines:	257

---

💛 - Coveralls

[vemv]

Hey there!

First of all kudos for the debugging rampage 👏

What would you think of PRing against setup-clojure?

I wouldn't mind keeping nvd-clojure red for a while - in the end I know that all tests are passing.

[seancorfield]

I don't know enough TypeScript to submit a PR against setup-clojure 😄 I created an issue there (linked above) and DeLaGuardo said he'd take a look later today.

Definitely sounds reasonable at this point to keep nvd-clojure red until setup-clojure is fixed so feel free to close this out.

[rm-hull]

@seancorfield dont worry about the commits on the branch, we usually squash/merge anyway

[vemv]

The diff is small enough that it can be easily reverted later.

Thanks again for the efforts! 😊