Test coveralls with other CI services.

[xd009642]

This stems from https://github.com/xd009642/coveralls-api/issues/1 currently the code is implemented but I ideally need people using these ci tools to try it out and see if it works better with coveralls.

Listed CI services are:

• [x] Travis
• [x] TravisPro
• [x] Circle
• [ ] Semaphore
• [x] Jenkins
• [ ] Codeship
• [x] gitlab CI
• [x] github actions

[Mossop]

FWIW I've managed to use this to upload to coveralls from Azure pipelines (https://github.com/FractalBrew/file-store-rs/blob/master/azure-pipelines.yml#L61)

[jonhoo]

The biggest issue with this is that the codecov token needs to be made available to pull requests, but that's an issue with Azure, not with tarpaulin. See also the re-useable Azure Pipelines component here https://github.com/crate-ci/azure-pipelines/blob/master/azure/coverage.yml and the coverage over at https://crate-ci.github.io/azure-pipelines/setup.html#code-coverage.

[xd009642]

Oooh I'll put a link to the azure repo you linked in the readme @jonhoo :+1:

[mathstuf]

I have Tarpaulin running under GitLab-CI here: https://gitlab.kitware.com/ben.boeckel/rust-git-workarea/-/jobs/4684893. Here's the diff to add support. Haven't done the work to get it to show up anywhere else yet.

[xd009642]

I've got gitlab mentioned in the readme now though that might be just how to get gitlab coverage working I found getting tarpaulin working on it was as easy as Travis

[notquiteamonad]

I have it working on GitHub Actions in samueldple/date_time if that's of interest to anyone using this workflow

[xd009642]

See personally I'd think of that as pretty self-explanatory no weird things or things to trip you up. Compared to for instance running tarpaulin from docker or the fact that travis needs you to set sudo: required. But I am starting to wonder if this project could benefit from a folder with a collection of bare bones config files for various CI services that people could refer to as a starting point.

But then it's work to maintain them and I only use travis or github actions personally so I won't spot any updates that are required so it relies on people having the examples not work anyway...

Anyone have any thoughts?

[mathstuf]

Maybe just pointing to example repos is good enough? I suggest only taking volunteers rather than seeking out examples (that way if they change CI backend, there's a chance there'd be a signal back here to update links).

[xd009642]

confirmed circle can work via docker by talking to a tarpaulin user

[xd009642]

Closing because it's been 3 years with no issues reported on other CI platforms