Ci azure to gh - #399
Open
IonutMuthi wants to merge 7 commits into
Open
Conversation
Add a push trigger for v* tags to build.yaml so the macOS wheel upload to testPyPI can fire on version tags, matching the Azure pipeline's release behavior. Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
Extend build_macos to a dual-arch matrix (macos-13 x64 + macos-14 arm64), building per-version Python wheels (3.9-3.14) and uploading them to testPyPI on v* tags. Bump its actions to checkout@v6 / setup-python@v7 / upload-artifact@v7 and set ARTIFACTNAME for the packaging scripts. Add a native build_windows job on windows-2022 that reuses the existing CI/windows/*.ps1 scripts unchanged by supplying the Azure environment variables they expect. It builds libm2k once, produces wheels for 3.9-3.14, and uploads the system-setup installer .exe and the win64 folder tree as artifacts (no PyPI upload, matching Azure). The shared CI/ scripts are reused as-is; the entire port lives in the workflow YAML. Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
The runner context is not available in a job-level env: block, so
${{ runner.temp }} there made GitHub reject build.yaml at parse time
(every run was a startup failure with zero jobs). Use
${{ github.workspace }} instead, which is valid at job-env scope, and
apply it consistently to the two artifact upload paths.
Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
libm2k.iss.cmakein hard-codes the Azure DevOps directory layout (sources at D:\a\1\s, build root at D:\a\1). On GitHub Actions the source dir is D:\a\libm2k\libm2k, so Inno Setup aborted reading the LicenseFile "D:\a\1\s\LICENSE" and every Source: path was wrong too. Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
IonutMuthi
force-pushed
the
ci_azure_to_gh
branch
from
August 6, 2026 13:32
91766ce to
de0b513
Compare
Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
IonutMuthi
force-pushed
the
ci_azure_to_gh
branch
from
August 7, 2026 05:48
de0b513 to
6e31028
Compare
Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
Signed-off-by: IonutMuthi <Ionut.Muthi@analog.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Port Azure macOS and Windows builds to GitHub Actions
Extend build_macos to a dual-arch matrix (macos-13 x64 + macos-14
arm64), building per-version Python wheels (3.9-3.14) and uploading
them to testPyPI on v* tags. Bump its actions to checkout@v6 /
setup-python@v7 / upload-artifact@v7 and set ARTIFACTNAME for the
packaging scripts.
Add a native build_windows job on windows-2022 that reuses the
existing CI/windows/*.ps1 scripts unchanged by supplying the Azure
environment variables they expect. It builds libm2k once, produces
wheels for 3.9-3.14, and uploads the system-setup installer .exe and
the win64 folder tree as artifacts (no PyPI upload, matching Azure).
The shared CI/ scripts are reused as-is; the entire port lives in the
workflow YAML.