-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fix acceptance test regressions caused by .NET6 release #157
Comments
here is a log dump of a failed run:
|
To me it looks like we are automatically installing the latest .NET SDK (Version: 6.0.100). But this isn't compatible with the
My naive idea is that we should update the runtime buildpack to parse the |
There are two issues here, I think:
The first point is relatively straightward to support, I suspect: we can install both .NET 6.0 and .NET Core 3.1 SDKs side-by-side, which should allow us to build either. I'm assuming it doesn't matter too much if the Docker image we use when building is larger than it really needs to be. The second point is trickier, as we don't want to deploy an image that is larger than it needs to be. We may not need to parse the TargetFramework from the csproj file though - we may find that after publishing, there's sufficient information in the output JSON files (that live alongside the binaries) to give us the information we need. That has an advantage over parsing csproj files, in that project files could do all kinds of complex tricks that we'd either have to not support or do significant work in order to replicate msbuild logic. The output JSON file should be a lot simpler to handle - but we'll need to investigate what we end up with in each case. |
@jskeet in this case the tests that started failing were for the GCP Buildpacks, which install all tools, SDKs etc at build time. It looks like our current logic for determining which .NET SDK we should install is:
I am wondering if we can be a bit smarter in step#3. I guess what would need is for Microsoft to expose an API that allows us to ask for "the latest SDK version compatible with this target framework". Maybe they already do and we just need to figure out how to construct the proper URL. |
Ahh nice, that makes sense. |
Trying to use the build pack with a .NET 6.0 application now fails as well. It was working with preview7, but I'm getting the same error above, even when explicitly specifying --env=GOOGLE_RUNTIME_VERSION=6.0.100. This was working a couple of months ago. |
Hi @jjdelorme, thanks for reporting your issue. I have a fix for this and it will likely be available late next week. |
Hi @spew, any updates on this? Thank you! |
Hello @jjdelorme thanks for asking. I'm behind on this one but should have a fix out by end of year. |
Hi @spew, is there an update on supporting .NET 6 in buildpacks? |
Hi @meteatamel I have submitted 1 out of 3 commits remaining to get .NET6 working, I am hoping to get them all in by next week (they are all complete). You can take a look at the first commit here: dac47e0 |
Just got another commit in: 3ea8b29 There is one more coming and then .NET 6 should work. |
Thanks for the update. I'll be the first one to try! :-) |
Woot! I'll be #2 ;-).
…On Thu, Feb 3, 2022 at 2:59 AM Mete Atamel ***@***.***> wrote:
Thanks for the update. I'll be the first one to try! :-)
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARTPW52GQDPYXW6DBINWMCDUZIYVZANCNFSM5HZIZUMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Me 3 🤩 |
This should be fixed, I just built a sample .NET 6.0 application with the following:
|
Please do let me know of any issues. |
@spew With your changes, it is not necessary to specify |
It is not necessary to specify When .NET 7 comes out, assuming nothing changes about the download URLs / untarring, and the |
Just confirming it worked for .NET 6! Thank you! |
Thanks for your work, @spew. I can also confirm it works.
If that is the case, you have essentially solved #89 as well. I'll go ahead and close that issue. |
Thanks, glad to hear that it works for all of you as well! |
Whoo! Thanks for the fix, works great for .NET 5 and 6. |
It looks like the .NET6 release broke many of our acceptance tests. I would have expected the dotnet runtime buildpack to automatically respect the version in the .csproj but it seems this is not the case. For now we pinned the
GOOGLE_RUNTIME_VERSION
in all the acceptance tests but we should find a way to remove this. We should also add some .NET6 specific acceptance tests.The text was updated successfully, but these errors were encountered: