-
Notifications
You must be signed in to change notification settings - Fork 867
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
Migration to .NET 6
(OpenSSL 3.0
and M1
architecture support)
#3922
Comments
Given that .NET Core 3.1 is EOL on 13th December 2022 and the .NET 6 move appears to be a pre-requisite for Ubuntu 22.04 support, is there a view on the likely ETA for .NET 6 support to drop? |
Just out of curiosity... |
We're now past the End of Support date for .Net Core 3.1. Is there any timeline available yet for when the .Net 6 migration is expected to be complete and released to users? |
Another month passed by. What's the status of this? @alexander-smolyakov |
Hey @MichelZ, I'm no longer working on this project. Probably @kirill-ivlev @LiliaSabitova @max-zaytsev could share the current status of this migration. |
Not sure why it hasn't been posted here previously, but worth reading: https://devblogs.microsoft.com/devops/upgrade-of-net-agent-for-azure-pipelines/ The current (as of writing) pre-release .NET build agent version is at https://github.com/microsoft/azure-pipelines-agent/releases (see the v3.x releases further down the page) |
Huge thanks for calling that out, @alexisatkinson. It's really frustrating to know that my team could have begun testing the MacOS arm64 runner months ago if Microsoft had just linked that announcement here. |
@sphanley sorry for the lack of updates in this ticket, in general, we have completed all required testing and started to provide public releases, you can find it on our Releases page. We will update this ticket once the agent will roll out in the main distribution channel. |
@kirill-ivlev It would be nice to have a way to update without reinstalling. |
@kirill-ivlev is there any estimation on when this will be rolled out to the main channel? |
Looks like everything is completed. Do we have a timeline for when this will merged? |
So, if I download the latest pre-release version sed -i "s@liblttng-ust0@liblttng-ust1@g" bin/installdependencies.sh
sed -i "s@libssl1\.1@libssl3@g" bin/installdependencies.sh
sed -i "s@libicu67@libicu70@g" bin/installdependencies.sh Hope these get actually incorporated into the project, but for anyone else this might be all you really need right now to get it running on the almost a year old Ubuntu LTS. |
Is there any plan to add the support for Windows ARM64? Or the Windows x64 release from the table is considered the coverage for Windows ARM64 arch as well? |
I see that the last two 3.x agent releases are no longer marked "prerelease". Does this mean it's considered to be stable and official at this point? Has there been any communication on the topic? |
It has been pushed to updates, you can update to 3.x from web UI |
Description
At the moment Azure Pipelines Agent targets the
.NET Core
v.3.1
. We need to migrate it to.NET 6
to provide support for:M1
architectureCurrent progress
.Net 6
M1
platformTesting
Breaking changes
AZP_AGENT_USE_LEGACY_HTTP
agent knob will be deprecated - Related announcementQuestions
TBD
Mitigation ways
TBD
The text was updated successfully, but these errors were encountered: