Repository navigation
FIX: Restore release package pipeline - #900
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PR Performance Report✅ No regression detectedNo consistent slowdowns detected across all 2 environments. 0 IMPROVEMENTS 0 SLOWDOWNS 2/2 ENVIRONMENTS Coverage: 2 of 2 environments completed. Advisory result; does not block merging. Performance diagnosticsPhase times are inclusive diagnostics and must not be added together. They identify where measured time changed, not why it changed. No affected phases or call-count changes were recorded. All database tasks and timingsUnix / SQL Server 2022
Unix / SQL Server 2025
Build and measurement detailsPR head:
A consistent change requires more than 20% median paired movement, at least 1 ms between the median runtimes, and at least 80% of pairs exceeding the relative threshold in the same direction. A slowdown without enough pair agreement is reported as inconsistent. The displayed change is the median of paired before-and-after ratios. It is not recalculated from the two displayed median runtimes. Both revisions use profiling-enabled builds on the same agent and database, with alternating order and discarded warmups. Results are diagnostic and do not represent production-wheel latency. Raw samples and logs are attached to the ADO run as |
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are reported for the switch to Quay images and added container-start retries.
No open issues 🎉
What changed in this PR
This PR restores Linux wheel image pulls on hosted 1ES agents by switching from GHCR imports to public PyPA images on Quay.
Changes:
- Uses Quay for both manylinux and musllinux images while preserving image variants and architecture selection.
- Adds up to five retries to the container-start task for transient failures.
| File | Description |
|---|---|
OneBranchPipelines/stages/build-linux-single-stage.yml |
Switches image sources to Quay, updates explanatory comments, and adds container-start retries. |
Review effort: Balanced
📊 Code Coverage Report
Diff CoverageDiff: main...HEAD, staged and unstaged changesNo lines with coverage information in this diff. 📋 Files Needing Attention📉 Files with overall lowest coverage (click to expand)mssql_python.pybind.performance_counter.hpp: 0.7%
mssql_python.pybind.logger_bridge.cpp: 57.9%
mssql_python.pybind.ddbc_bindings.h: 64.5%
mssql_python.pybind.logger_bridge.hpp: 70.8%
mssql_python._native_fetch.py: 77.7%
mssql_python.__init__.py: 80.8%
mssql_python.pybind.ddbc_bindings.cpp: 81.4%
mssql_python.pybind.row_mapping_cache.hpp: 81.5%
mssql_python.pybind.connection.connection_pool.cpp: 82.5%
mssql_python.pybind.connection.connection.cpp: 83.1%🔗 Quick Links
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Work Item / Issue Reference
Summary
Restore the release package pipeline after four independent blockers.
committedsentinel required by the ADO manual-run form.committedto an empty override so Official builds use the pinned public release fromeng/versions/mssql-python-rs.version.The native-fetch test passed PR validation on Python 3.13.17 but failed the release pool on Python 3.13.11 because the pipelines float different patch versions. No production native-fetch behavior changes.
Validation
maininto this branch before applying the unblock.MSSQL_PYTHON_RS_VERSIONto an empty value andeffectiveOneBranchTypetoOfficial.timeoutInMinutesto 240.git diff --checkpassed.