Repository navigation
Use EO and stable pools for DevDiv analysis - #26302
Stella Huang (StellaHuang95) merged 1 commit into
Conversation
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
|
Reviewed commit: Result: 🔴 Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: C:\Users\rchiodo\AppData\Local\Programs\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "4ccfe357899ae710fbfb4e58cacfcd52dd450b5ec42f7486a02ff1e6fa8a03a7": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Test runs: none recorded. |
a26dd50 to
124a5fc
Compare
Keep ordinary SDL and static analysis on EO, and move protected API Scan work to the supported stable pool. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
124a5fc to
cef1a31
Compare
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
96e6e78
into
microsoft:main
Summary
AzurePipelines-EOpoolVSEngSS-MicroBuild2022-1ESto supportedVSEng-MicroBuildVSStable, retainingos: windowsAll protected work now uses the supported stable pool, while ordinary SDL/static analysis remains on EO.
Validation
git diff --checkTracking: microsoft/pyrx#10073