You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workflow was expected to continue running on ubuntu 24.4 and latest dotnet sdk versions pre-installed.
Actual behavior
If not manually installing requested globaljson sdk version, pre-installed sdk version on 24.4 isn't able to run my code.
and 24.4 doesn't recognize sqlcmd command.
Repro steps
Switching between ubuntu 22.4 and 24.4 back and forth identifies the root cause.
Typically by running dotnet --list-sdks on each to list -pre-installed sdk versions.
The text was updated successfully, but these errors were encountered:
eventsourcer
changed the title
ubuntu-latest has ruined my dotnet workflow setup by running to 24.x
ubuntu-latest has ruined my dotnet workflow setup by jumping to 24.x
Jan 20, 2025
Description
Looks like Actions runner recently bumped to ubuntu
24.x
when specified withruns-on: ubuntu-latest
.My dotnet workflow setup was working fine using
ubuntu-latest
shipped with a list of pre-installed dotnet sdks including my requestedglobaljson
.But now the new ubuntu version i.e.
24.x
not only isn't resolving dotnet sdk but doesn't even recognizesqlcmd
command.After troubleshooting this required me to fix the ubuntu tag to
22.4
as shown on my workflow.Platforms affected
Runner images affected
Image version and build link
Sample failed workflow:
https://github.com/eventstorage/eventstorage/actions/runs/12857436891/job/35845293717
Is it regression?
ubuntu-22.4 works fine: https://github.com/eventstorage/eventstorage/actions/runs/12869120817
Expected behavior
Workflow was expected to continue running on ubuntu
24.4
and latest dotnet sdk versions pre-installed.Actual behavior
If not manually installing requested globaljson sdk version, pre-installed sdk version on
24.4
isn't able to run my code.and
24.4
doesn't recognizesqlcmd
command.Repro steps
Switching between ubuntu
22.4
and24.4
back and forth identifies the root cause.Typically by running
dotnet --list-sdks
on each to list -pre-installed sdk versions.The text was updated successfully, but these errors were encountered: