Skip to content

[WIP] Modernizing repo and improving ease of use #14

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

Open
wants to merge 49 commits into
base: master
Choose a base branch
from

Conversation

cloudRoutine
Copy link
Member

My primary goal was to get this repo setup so people can clone it run build.cmd/build.sh and have everything compile and run without any manual configuration.

To do this I switched to using paket and FAKE for the build process and sqlite & sqlprovider for the tests.

I've almost gotten all of the tests passing, but a few are failing with errors I don't really understand.

@cloudRoutine cloudRoutine force-pushed the reorg branch 16 times, most recently from ed1c796 to a615344 Compare March 24, 2017 02:15
@cloudRoutine
Copy link
Member Author

@jamescheney could you enable appveyor builds for the repo too?

it was a real pain but I've finally got the CI running properly for both travis and appveyor
https://travis-ci.org/fsprojects/FSharp.Linq.ComposableQuery/builds/214518947

you can see the appveyor results for my fork here https://ci.appveyor.com/project/cloudRoutine/fsharp-linq-composablequery

sorry it took so long for me to get back to this

@dsyme
Copy link
Contributor

dsyme commented Mar 24, 2017

could you enable appveyor builds for the repo too?

@jamescheney - if you like we can make @cloudRoutine a joint administrator on this project and the CI as well. He's an active and trustworthy contributor to many F# repos

@jamescheney
Copy link
Contributor

@cloudRoutine - I think I've done this (https://ci.appveyor.com/project/jamescheney/fsharp-linq-composablequery) but don't really know what I'm doing, so...

@dsyme - That sounds great to me; I unfortunately haven't been able to make much progress on this so see no reason to stand in the way of someone else who can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants