Skip to content

Use global.json for SDK version in CI workflows#193

Draft
dkropachev wants to merge 1 commit into
masterfrom
fix/ci-use-global-json-sdk
Draft

Use global.json for SDK version in CI workflows#193
dkropachev wants to merge 1 commit into
masterfrom
fix/ci-use-global-json-sdk

Conversation

@dkropachev
Copy link
Copy Markdown
Collaborator

Summary

  • CI integration-test jobs (especially net6/net7) were picking up the runner's pre-installed .NET SDK 10.0.x instead of the intended 9.0.x, because setup-dotnet only installed the target framework runtime without matching the SDK version from global.json
  • This caused flaky build failures (MSB4018 GenerateDepsFile IOException on ScyllaDB.deps.json) due to parallel build race conditions in the newer SDK
  • Switch all setup-dotnet steps across main.yml and publish.yml to use global-json-file: global.json, keeping a single source of truth for SDK version

Test plan

  • CI passes on this PR (especially the integration-tests (PRIOR, net6, 6.0.x) job that was failing)
  • Verify the build log shows SDK 9.0.x being used instead of 10.0.x

CI jobs were using a runner-preinstalled .NET SDK 10.0.x instead of the
intended 9.0.x because the setup-dotnet action only installed the target
framework runtime without the SDK version specified in global.json. This
caused build race conditions (MSB4018 GenerateDepsFile IOException) due
to behavioral differences in the newer SDK.

Switch all workflows to use global-json-file parameter so the SDK
version is always read from global.json, keeping a single source of
truth.
Copy link
Copy Markdown

@sylwiaszunejko sylwiaszunejko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI fails due to no global.json file

@dkropachev dkropachev marked this pull request as draft February 23, 2026 13:21
@dkropachev
Copy link
Copy Markdown
Collaborator Author

CI fails due to no global.json file

Sorry, should not have tagged you, it is not ready yet.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants