Set up CI - Githubissues

true-myth / true-myth-csharp

A library for safer optional programming in C♯.

https://true-myth.github.io/true-myth-csharp

MIT License

4 stars 1 forks source link

Set up CI #6

Closed chriskrycho closed 6 years ago

chriskrycho commented 6 years ago

Best bet is probably Appveyor, which does free CI and CD for open source projects.

Once we have the integration written, we'll block merges to master on passing tests.

chrisriesgo commented 6 years ago

FYI - I set up a quick Appveyor project against my Fork to keep any eye on build status until one is set up against the upstream repo.

chriskrycho commented 6 years ago

Dang, I forgot that I have to enable it as a maintainer. Can you open a PR with the YAML file, and I’ll flip the switch here to get it integrated?

aggieben commented 6 years ago

I've got a working build on myget.org. Badge:

aggieben commented 6 years ago

After difficulty with AppVeyor support, I've started working on this on my own account. MyGet is sufficient in a pinch (we need a build right now and can't wait until appveyor is straightened out, etc), but i'll eventually get this worked out.

aggieben commented 6 years ago

I have this set up on AppVeyor now, although I never really finished. Badge added to the README. Will keep working as I can.

chriskrycho commented 6 years ago

Solid. Closing accordingly!

aggieben commented 5 years ago

I've done this again on Azure Pipelines; it is much more comprehensive (tests against all three supported platforms and both supported framework targets), and more flexible for helping with automating releases, is triggered to verify PRs, etc.

https://dev.azure.com/true-myth/TrueMyth/_build?definitionId=1&_a=summary

CI builds get pushed here: https://www.myget.org/feed/true-myth/package/nuget/TrueMyth. They only build on changes to master; builds triggered by PRs do not create CI artifacts.