0.1x ci

[technoweenie]

Backports our current CircleCI/CodeClimate config over from master. Hopefully we can then test and merge #1013.

[technoweenie]

Our test suite changes in master were never backported to this branch. Removing linting from the circle ci config was easy enough, but now the tests don't run.

bundle exec rspec --require rspec_junit_formatter --format progress --format RspecJunitFormatter --out ~/test-results/rspec/results.xml

bundler: command not found: rspec

I think we have a couple options:

• Try to update this branch to run test/unit.
  • This doesn't seem trivial, since they were written to run on Travis, and not in a Docker image. Running rake test complains about the lack of lsof (used to check for the faraday test server thing).
• Backport all of the test suite, circle ci, and rubocop changes to 0.1x
• Release current master as v0.16.0 into the new stable branch 0.16.x. This could essentially be our v1.0 RC branch.

[olleolleolle]

According to CircleCI, there are variant Docker images, tagged with lots of suffixes.

https://circleci.com/docs/2.0/circleci-images/#ruby

Perhaps the ones we use could try the 2.6-stretch suffix, to make available lots of surrounding lsof etc?

Well, all of the image: keys in this branch's CircleCI configuration would have to be updated.

[olleolleolle]

Suggested change

	- image: circleci/ruby:2.6
	- image: circleci/ruby:2.6-stretch

[technoweenie]

Closing in favor of just shipping v0.16.0 and a 0.16.x branch.

[BobbyMcWho]

@technoweenie do you wanna un-delete this branch? I can copy/paste these changes, but would rather just cherry-pick

[technoweenie]

This PR sets up Circle CI, which we've already transitioned from. So I don't think it's makes sense to bring this back.

[BobbyMcWho]

Ah, I wasn't aware that the project was moving away from circleci