From 32de25830ff1a2b4e81bc8e192a9d70405825493 Mon Sep 17 00:00:00 2001 From: Stephen Walsh Date: Sat, 7 Nov 2026 20:08:33 -0600 Subject: [PATCH] Fix the results stage and the redirect address on the run-locally pages --- src/content/docs/graphql/guides/run-locally.mdx | 10 ++++++---- src/content/docs/lambda/guides/run-locally.mdx | 8 +++++--- src/content/docs/mcp/guides/run-locally.mdx | 10 ++++++---- src/content/docs/minimalapi/guides/run-locally.mdx | 10 ++++++---- src/content/docs/webapi/guides/run-locally.mdx | 10 ++++++---- 5 files changed, 29 insertions(+), 19 deletions(-) diff --git a/src/content/docs/graphql/guides/run-locally.mdx b/src/content/docs/graphql/guides/run-locally.mdx index fa51c50..c10c920 100644 --- a/src/content/docs/graphql/guides/run-locally.mdx +++ b/src/content/docs/graphql/guides/run-locally.mdx @@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data dotnet run --project ./src/Presentation ``` - `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7331](https://localhost:7331), and on `https://localhost:7331`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. + `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7331](https://localhost:7331), and on `http://localhost:7330`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. ```bash @@ -98,15 +98,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need. | Stage | What it does | | --- | --- | | `build` | Restores and builds the solution | -| `test` | Runs every test with coverage | -| `coverage` | Exports the coverage report to your machine | +| `test` | Runs every test with coverage, and saves the result instead of failing the build | +| `results` | Exports the test results, the coverage report and the exit code to your machine | | `publish` | Publishes the Presentation project | | `run` | The image you deploy | ```bash -docker build . --target coverage --output type=local,dest=out +docker build . --target results --output type=local,dest=out ``` +A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it. + ## Stamp a version ```bash diff --git a/src/content/docs/lambda/guides/run-locally.mdx b/src/content/docs/lambda/guides/run-locally.mdx index da3db0f..80ad75e 100644 --- a/src/content/docs/lambda/guides/run-locally.mdx +++ b/src/content/docs/lambda/guides/run-locally.mdx @@ -68,15 +68,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need. | Stage | What it does | | --- | --- | | `build` | Restores and builds the solution | -| `test` | Runs every test with coverage | -| `coverage` | Exports the coverage report to your machine | +| `test` | Runs every test with coverage, and saves the result instead of failing the build | +| `results` | Exports the test results, the coverage report and the exit code to your machine | | `publish` | Publishes the Presentation project | | `run` | The Lambda image you deploy | ```bash -docker build . --target coverage --output type=local,dest=out +docker build . --target results --output type=local,dest=out ``` +A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it. + ## Stamp a version ```bash diff --git a/src/content/docs/mcp/guides/run-locally.mdx b/src/content/docs/mcp/guides/run-locally.mdx index 2e64fc8..7e98751 100644 --- a/src/content/docs/mcp/guides/run-locally.mdx +++ b/src/content/docs/mcp/guides/run-locally.mdx @@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data dotnet run --project ./src/Presentation ``` - `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7321](https://localhost:7321), and on `https://localhost:7321`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. The server is at `/mcp`. + `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7321](https://localhost:7321), and on `http://localhost:7320`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. The server is at `/mcp`. ```bash @@ -117,15 +117,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need. | Stage | What it does | | --- | --- | | `build` | Restores and builds the solution | -| `test` | Runs every test with coverage | -| `coverage` | Exports the coverage report to your machine | +| `test` | Runs every test with coverage, and saves the result instead of failing the build | +| `results` | Exports the test results, the coverage report and the exit code to your machine | | `publish` | Publishes the Presentation project | | `run` | The image you deploy | ```bash -docker build . --target coverage --output type=local,dest=out +docker build . --target results --output type=local,dest=out ``` +A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it. + ## Stamp a version ```bash diff --git a/src/content/docs/minimalapi/guides/run-locally.mdx b/src/content/docs/minimalapi/guides/run-locally.mdx index 2c1b9b7..8f34a90 100644 --- a/src/content/docs/minimalapi/guides/run-locally.mdx +++ b/src/content/docs/minimalapi/guides/run-locally.mdx @@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data dotnet run --project ./src/Presentation ``` - `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7311](https://localhost:7311), and on `https://localhost:7311`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. + `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7311](https://localhost:7311), and on `http://localhost:7310`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. ```bash @@ -91,15 +91,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need. | Stage | What it does | | --- | --- | | `build` | Restores and builds the solution | -| `test` | Runs every test with coverage | -| `coverage` | Exports the coverage report to your machine | +| `test` | Runs every test with coverage, and saves the result instead of failing the build | +| `results` | Exports the test results, the coverage report and the exit code to your machine | | `publish` | Publishes the Presentation project | | `run` | The image you deploy | ```bash -docker build . --target coverage --output type=local,dest=out +docker build . --target results --output type=local,dest=out ``` +A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it. + ## Stamp a version ```bash diff --git a/src/content/docs/webapi/guides/run-locally.mdx b/src/content/docs/webapi/guides/run-locally.mdx index d160f18..29295bd 100644 --- a/src/content/docs/webapi/guides/run-locally.mdx +++ b/src/content/docs/webapi/guides/run-locally.mdx @@ -17,7 +17,7 @@ There are two ready-made environments. `local` is for `dotnet run`: sample data dotnet run --project ./src/Presentation ``` - `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7341](https://localhost:7341), and on `https://localhost:7341`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. + `launchSettings.json` sets the environment to `local` and listens on [https://localhost:7341](https://localhost:7341), and on `http://localhost:7340`, which redirects to it. If your browser or `curl` doesn't trust the .NET development certificate yet, run `dotnet dev-certs https --trust` once. ```bash @@ -91,15 +91,17 @@ The `Dockerfile` has a stage for each job, so you can build only what you need. | Stage | What it does | | --- | --- | | `build` | Restores and builds the solution | -| `test` | Runs every test with coverage | -| `coverage` | Exports the coverage report to your machine | +| `test` | Runs every test with coverage, and saves the result instead of failing the build | +| `results` | Exports the test results, the coverage report and the exit code to your machine | | `publish` | Publishes the Presentation project | | `run` | The image you deploy | ```bash -docker build . --target coverage --output type=local,dest=out +docker build . --target results --output type=local,dest=out ``` +A failing test doesn't fail the build, so the results still come out. Check `out/exit-code`: anything other than `0` means a test failed, and a pipeline built on these stages should fail on it. + ## Stamp a version ```bash