Repository navigation
CI test publishing and misc cleanups - #12441
Alan Zimmer (alzimmermsft) wants to merge 6 commits into
Conversation
commit: |
|
All changed packages have been documented.
Show changes
|
There was a problem hiding this comment.
🔵 Needs a closer look
A native Azure DevOps run is needed to validate matrix TestArguments expansion in publishing conditions and Maven cache restore/save behavior, since the added JavaScript tests do not exercise Azure’s expression engine.
No open issues 🎉
What changed in this PR
This PR improves test-failure visibility in the language-emitter CI pipelines by publishing results to Azure DevOps. It also adds Maven dependency caching and reduces Java build-log noise.
Changes:
- Enable JUnit and TRX reports and publish results from test-producing jobs, including failed runs.
- Cache Maven artifacts without caching feed credentials, and suppress transfer-progress output.
- Add regression tests for reporting configuration, publishing conditions, and caching.
| File | Description |
|---|---|
packages/http-client-python/tests/tox.ini |
Write separate JUnit reports for each pytest environment. |
packages/http-client-python/eng/scripts/Test-Packages.ps1 |
Document collected test-report paths. |
packages/http-client-python/emitter/vitest.config.ts |
Enable JUnit reporting in Azure DevOps. |
packages/http-client-java/generator/http-client-generator-clientcore-test/Generate.ps1 |
Suppress Maven transfer progress during smoke builds. |
packages/http-client-java/eng/scripts/Test-Packages.ps1 |
Run emitter tests with console and JUnit reporters. |
packages/http-client-java/eng/scripts/Build-Packages.ps1 |
Suppress transfer progress during formatting checks. |
packages/http-client-csharp/eng/scripts/Test-Packages.ps1 |
Enable emitter JUnit and generator TRX reports. |
packages/http-client-csharp/eng/scripts/Get-Spector-Coverage.ps1 |
Enable TRX reports for Spector tests. |
eng/emitters/pipelines/templates/steps/test-step.yml |
Publish language-specific JUnit and C# TRX results. |
eng/emitters/pipelines/templates/steps/build-step.yml |
Publish Java generator results after builds. |
eng/emitters/pipelines/emitter-ci.test.ts |
Test caching, report configuration, and publishing conditions. |
eng/common/pipelines/templates/steps/maven-authenticate.yml |
Cache Maven artifacts by OS, stage, and POM contents. |
.chronus/changes/UpdateTargetVersions-2026-9-29-10-7-0.md |
Record Java CI caching and result publishing. |
.chronus/changes/CiCachingAndTestPublishing-2026-9-29-14-33-2.md |
Record reduced Maven log verbosity. |
.chronus/changes/CiCachingAndTestPublishing-2026-9-29-11-43-1.md |
Record shared test-result publishing for Java and Python. |
Review effort: Balanced
Python emitter diffBaseline No changes to generated output. Rendered diff: inline on the run summary, or the emitter-diff-html artifact. Informational check (eng/emitter-diff); does not block the PR. |
|
You can try these changes here
|
Jorge Rangel (jorgerangel-msft)
left a comment
There was a problem hiding this comment.
c# emitter changes LGTM
Updated conditions to use coalesce for TestArguments variable. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Add test publishing to CI to make it easier to see what failed in the job. Also, clean up a few things in Java such as adding Maven caching to speed up CI and reduce log verbosity when building Maven packages.