-
Notifications
You must be signed in to change notification settings - Fork 5
#9 GitHub actions build pipeline - attempt 1 of ?? (yay for YAML) #32
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
Conversation
Just does a build and runs tests whenever we get a PR into dev or main, nothing fancy.
…w for future filtering and to give something to trigger a test run of the PR build pipeline.
WPF build dependencies require a Windows OS image for the build.
…and causing null reference exception, un-blocks DevChatter#9, See also DevChatter#34.
@benrick, after this PR is merged to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a simple set of build steps.
jobs: | ||
build: | ||
|
||
runs-on: windows-latest #Can't use anything else as WPF build has a windows dependency - waiting on .NET MAUI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I'm hopeful that MAUI will have all the cool stuff we want.
Obviously you will need to set-up the branch protection rules once it's in on your side. |
Step 1 of #9 providing an initial CI/CD build pipeline;
This is just the simple PR workflow that will compile the solution and run all the tests in the test project.
Since we may want to filter tests by category later, so ill add annotations to the existing unit tests for that, as it will also give me something to PR into my own main branch to test the triggers.
This also fixes #33 with the resolution of a null reference bug.