-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Workflow linting and test separation #3684
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3684 +/- ##
==========================================
+ Coverage 32.42% 32.58% +0.15%
==========================================
Files 1212 1212
Lines 63353 63353
Branches 4762 4759 -3
==========================================
+ Hits 20542 20641 +99
+ Misses 41766 41752 -14
+ Partials 1045 960 -85 ☔ View full report in Codecov by Sentry. |
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.
⛏ - for minor or nitpick changes
❓ - for questions
💭 - for open inquiry
🎨 - for suggestions / improvements
🌱 - for future improvements
- "main" | ||
- "rc" | ||
- "hotfix-rc" | ||
pull_request: |
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.
❓ The way I read this is that you want to build on any push to main/rc/hotfix-rc, and all pull requests? The main thing I'm concerned about is that with nothing listed under pull_requests
, that it's not clear PR branches will be built. Assuming I read it correctly, a comment indicating the behavior being relied upon here would be nice.
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.
That's correct, that an open-ended trigger applies to all of that type.
uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 # v4.1.0 | ||
|
||
- name: Set up dotnet | ||
- name: Set up .NET |
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.
⛏️ I'd keep this dotnet
to keep it consistent with the CLI command run on line 43.
@@ -445,7 +402,7 @@ jobs: | |||
if-no-files-found: error | |||
|
|||
build-mssqlmigratorutility: | |||
name: Build MsSqlMigratorUtility | |||
name: Build MSSQL migrator utility |
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.
⛏️ Here's another case where I think it's better to stick with the package name being built/installed. Or, barring that, fully spell out Microsoft SQL Server.
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.
There's a few places where "MSSQL" is used and this is traditionally the shorthand and image name, at least in a lot of places.
BW_TEST_DATABASES__1__CONNECTIONSTRING: "server=localhost;uid=root;pwd=SET_A_PASSWORD_HERE_123;database=vault_dev" | ||
# Default Dapper SqlServer | ||
BW_TEST_DATABASES__2__TYPE: "SqlServer" | ||
BW_TEST_DATABASES__2__CONNECTIONSTRING: "Server=localhost;Database=vault_dev;User Id=SA;Password=SET_A_PASSWORD_HERE_123;Encrypt=True;TrustServerCertificate=True;" |
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.
./Migrate.ps1
.
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.
Not sure what you're referring to here.
- name: Docker Compose down | ||
if: always() | ||
working-directory: "dev" | ||
run: docker compose down |
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.
❓ Is volume cleanup necessary?
dotnet --info | ||
nuget help | grep Version | ||
echo "GitHub ref: $GITHUB_REF" | ||
echo "GitHub event: $GITHUB_EVENT" |
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.
🎨 Since these are going to be seen by folks that might not know what they refer to, I'd be a bit more descriptive.
@@ -0,0 +1,57 @@ | |||
--- | |||
name: Testing |
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.
⛏️ Maybe "dotnet" or ".Net" testing -- since the database tests are specific, this should be as well.
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.
I kinda thought of this as the location for all logic-level and therefore "generic" tests, whereas the other file is specific infrastructure testing for a database.
jobs: | ||
testing: | ||
name: Run tests | ||
runs-on: ubuntu-22.04 |
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.
❓ Does this need to be tested on windows and *nix? I'm thinking mostly about path manipulation, fwiw, but it could also be important if we're running integration tests for IIS hosts.
Made a few more changes based on comments but left a few things alone, perhaps with some ambivalence around making the change or not and being careful about reaching too far here. My goal was almost entirely to tidy and better represent the test step, so I didn't want to make logic changes that materially affect our CI processes. |
New Issues
Fixed Issues
|
Type of change
Objective
Performs a number of cleanup tasks on wording and lint for YAML, and moves tests around for better alignment and organization.
Before you submit
dotnet format --verify-no-changes
) (required)