-
Notifications
You must be signed in to change notification settings - Fork 165
Replace Appveyor with GitHub Actions #391
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
Conversation
35796f7 to
133ec90
Compare
53eaa0a to
3459f3f
Compare
|
Sourcelink should be working now. Based on: https://devblogs.microsoft.com/nuget/introducing-source-code-link-for-nuget-packages/ Also tested generated packages with Nuget Package Explorer |
|
Thank. I'll put this PR aside for now to finish other things. Now there is no urgent need to build the release. In parallel, I will read the documentation on github actions and appveyor. As a result, I would like to choose the simplest and most understandable solution with a minimum of scripts. |
I agree. We can delete these files if we remove appveyor:
I agree. GitHub Actions is only a single script for a single action. We have three actions, so there are three independent scripts. |
|
Done. Start at 1 or 1001? |
|
I prefer 1. But I talked about GraphQL.NET, not server project. By the way, how to reset github build number? |
|
Would we not want a consistent build process for all the projects? We can reset the number by renaming the yml file, as noted in the comment in the yml file. |
Sure. I just drew attention to the fact that it is worth changing the counter in the already committed code in graphql-net. |
| .AddWebSockets(); | ||
| services.AddLogging(builder => | ||
| { | ||
| // prevent writing errors to Console.Error during tests (required for testing on ubuntu) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow! Does this cause the tests to fail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about allow to write logs on Windows?
if (RuntimeInformation.IsOSPlatform(OSPlatform.Linux))
{
// Do something
}There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can’t remember anymore. Maybe it just caused a bunch of extra output. I think it caused a failure though, without this change. I did write “required”...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, OK.
...s/Transports.Subscriptions.WebSockets.Tests/Transports.Subscriptions.WebSockets.Tests.csproj
Show resolved
Hide resolved
Co-authored-by: Ivan Maximov <[email protected]>
Co-authored-by: Ivan Maximov <[email protected]>
Co-authored-by: Ivan Maximov <[email protected]>
Co-authored-by: Ivan Maximov <[email protected]>
Co-authored-by: Ivan Maximov <[email protected]>
Co-authored-by: Ivan Maximov <[email protected]>
|
Thanks for this PR. One question left : VersionSuffix. I still don't understand why this is needed. |
|
It's not needed, per se. It just ensures that any local build will not have a "real" version number. Actually, nevermind. Since the default prefix has "preview" in it already, that should be covered. I'll remove that. |
Co-authored-by: Ivan Maximov <[email protected]>
sungam3r
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last suggestion is to move <VersionPrefix>4.1.0-preview</VersionPrefix> on the first line inside props section.
|
By the way, here I configured branches https://github.com/graphql-dotnet/server/settings/branches for both master and develop but in GraphQL.NET I can see only master rule https://github.com/graphql-dotnet/graphql-dotnet/settings/branches. |
This PR adds GitHub Actions (workflows) for the following purposes:
masterordevelop) and publish them to the GitHub Packages repository. Versions have the prefix specified in the build props file, with a suffix that increments starting a little above 1000.This does not publish to myget. This could be enabled by changing the
build.ymlfile a little.In order to have this code publish to Nuget, the API key for Nuget must be loaded into a NUGET_AUTH_TOKEN GitHub secret. See Settings > Secrets. Secrets cannot be read by workflows in forked repositories, so they are secure. Who holds the proper Nuget account? They will need to generate a new API key and punch it in.
I've tested as much as I can at this point. I'd prefer to merge, issue a release, and review the artifacts generated. It will not publish to nuget because it will not have an API key. If all is well, then add the NUGET_AUTH_TOKEN and delete and reissue the release.