Build Server Uses .Net 6.0, and DRY Out GitHub Actions Code #310
Conversation
We really need to figure out how to share steps across platforms...
… common stuff. Not entirely sure this is gonna work, but it seems worth a try.
… can't find that action. I love it when error messages are actually helpful!
…ed in the action.
…ut leaving in a bunch of run statements. I fully expect this will blow up, but maybe not...
|
Okay, I'm marking this as ready. The first commit does the .NET 6.0 part. The remainders are DRYing out the code, there's a commit for each Workflow build. No need to look at each one individually as most got reverted, but if you're curious what was tried, you can see the answer. Basically it's still not as DRY as I'd like (mainly due to required boilerplate), but my net lines of code is still negative so I think it's good enough for now. My goal here isn't to be an expert on GitHub Actions, and after last month's Serilog tangents, I'd prefer to keep this tangent short. |
|
looks like I can rebase #204 on this since the approach I took was pretty hacky, but it would be great to get unit tests running in CI |
|
Merging after 7+ days with no-review, and self-checking. |
Closes #307
Closes #309
GitHub Actions isn't the world's most advanced CI product, but I still managed to DRY it out after some research on how to do that. See #309 for more details about that. This currently uses Composite Actions, which seemed like the most appropriate tool for the job, although I'm still not entirely convinced just building for all 3 platforms in one job wouldn't be a superior (if perhaps slightly slower) approach.