-
Notifications
You must be signed in to change notification settings - Fork 75
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
Why not using travis (or another) ? #21
Comments
Yes I need to set it up. Maybe I will do that this week. I'll let you know if I need any help. |
If you want, this document really helps ! |
Excellent, thanks. |
@Kerosene2000, it can be useful only for the docs. Because you cannot test OpenCL in arbitrary travis machine :) |
That's right ! I didn't think of that 😄 |
No idea, I've never tried the travis before. |
here is a little help file somehow, I don't really know if that works 🍋 |
After some investigation, this won't be useful enough to warrant bothering with for now considering the constraints of an OpenCL environment. Eventually a comprehensive, cross-platform test suite will need to be set up but I'm not sure that travis will necessarily be the way to do it. Publishing documentation has been a simple shell script for quite some time and I see no reason to change that. |
Why not using travis to call
cargo build
,cargo test
for each commit ?Each pull request/commit can update the documentation...
I already use it on some of my rust libraries, so I can help you for that (I think) 😄
The text was updated successfully, but these errors were encountered: