Skip to content
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

Add GitHub actions CI #19

Merged
merged 3 commits into from
Mar 2, 2024
Merged

Add GitHub actions CI #19

merged 3 commits into from
Mar 2, 2024

Conversation

mqudsi
Copy link
Member

@mqudsi mqudsi commented Mar 2, 2024

Test under Linux, Windows, and macOS.

@mqudsi mqudsi force-pushed the github-actions branch 3 times, most recently from 74a23a1 to 93ecad0 Compare March 2, 2024 19:42
mqudsi added 3 commits March 2, 2024 14:25
Test under Linux, Windows, and macOS.

Configure actions/setup-dotnet to correctly test multiple .NET versions

We need to use a temporary global.json that contains the version of the .NET SDK
we want to run the tests under, as the default behavior is to run under the
greatest version installed regardless of what the project says.

Explicitly set framework for `dotnet` invocations

It seems `TargetFrameworks` is conflicting with our `global.json` CI step; we
are locking the SDK to a specific version but the csproj sometimes specifies a
higher target framework.

Use msbuild `-p` argument to specify TargetFrameworks override under CI

Revert CI build logs to "Normal" level

We've verified global.json is working and the correct version of the SDK is
invoked.
@mqudsi mqudsi merged commit c285022 into master Mar 2, 2024
6 checks passed
@mqudsi mqudsi deleted the github-actions branch March 2, 2024 20:27
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.

1 participant