-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distribute binaries? #110
Comments
So currently in terms of prebuilt binaries/docker-images there is a pre-built docker image for each release on stable (but nightly versions of releases will be included from the next release) and stable and nightly for latest develop. You can see details about the docker images here. Also, on github releases I get travis to upload a version of tarpaulin compiled with the latest stable at the time for any tagged releases. You also could install tarpaulin from the develop branch, although down to a dependency on syn this now looks like: I understand the github releases being stable isn't suitable and the docker stable/nightly might be on a nightly version that's isn't suitable. So if you have any more flexible solutions that don't require a great deal of time to maintain but are more automated I'm open to them. |
Nice! I'll look into it (after monday I think... currently in a rush) |
So I've actually set up travis properly so every commit into develop causes a docker hub automated build on develop with nightly and stable and also any previous releases. If there's anything more that could be useful let me know and I'll look into it 👍 |
Nice :) I'll try this week I hope. But I think this + the release tab on github is perfect. |
Yup. It's perfect. I close this |
You know since #100 I need to build my project with rust-nightly to get a correct coverage report.
Currently the latest nightly gives me another error related to the sqlite database. So, since one month, I use
nightly-2018-03-18
It was working until some builds where
cargo install cargo-tarpaulin
breaks. This is the best part of the log:I don't think you or me have the time to do that for now, but maybe it could be awesome to directly distribute a pre-built version of tarpaulin? This will allow users to avoid this kind of errors or even to dramatically reduce the CI time.
I think I'll make a docker for this.
Have a nice day!
The text was updated successfully, but these errors were encountered: