Skip to content
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

Add AppVeyor CI #38

Open
zvirja opened this issue Apr 12, 2018 · 3 comments
Open

Add AppVeyor CI #38

zvirja opened this issue Apr 12, 2018 · 3 comments

Comments

@zvirja
Copy link
Contributor

zvirja commented Apr 12, 2018

We definitely need CI for this project, otherwise it's very dangerous to merge the PRs. Everything is ready for CI (configuration file is already present), you need to do a couple of things only:

  • Go to AppVeyor and create a build for this repo (a few clicks).
  • If you wish to enable automatic release after you create a tag (via GitHub UI), please update the appveyor.yml file and specify the NuGet API Key (encrypted) to the NUGET_API_KEY variable.
@moodmosaic
Copy link
Owner

I always run a build on my local before merging a PR, plus this repo didn't receive that many PRs until now, but yeah, this can be useful 👍

@moodmosaic
Copy link
Owner

I think we need something like this just to be able to grab the generated NuGet Packages and publish them. Personally, I no longer use Visual Studio and having troubles running the build scripts as-is from #30.

Even on Windows, with .NET Core installed, build scripts don't seem to work as per #42.

@zvirja
Copy link
Contributor Author

zvirja commented Jul 18, 2018

Answered in #42 - build scripts should be rewritten if VS installation is missing, so we use dotnet instead of MsBuild

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

No branches or pull requests

2 participants