CI: Migrate pyedb CI to AEDT 2026.1#2014
Merged
svandenb-dev merged 70 commits intomainfrom Apr 14, 2026
Merged
Conversation
# Conflicts: # src/pyedb/workflows/utilities/cutout.py # tests/conftest.py
# Conflicts: # src/pyedb/generic/design_types.py # tests/system/test_edb.py
…grpc-in-memory_dm_fixes_0
ecoussoux-ansys
requested review from
maxcapodi78 and
svandenb-dev
as code owners
github-actions
bot
added
documentation
…/migrate-to-aedt-26r1
# Conflicts: # src/pyedb/grpc/database/modeler.py
…/migrate-to-aedt-26r1 # Conflicts: # .github/workflows/ci-pr.yml # .github/workflows/ci-release.yml
…/migrate-to-aedt-26r1
maxcapodi78
previously approved these changes
Apr 13, 2026
…/migrate-to-aedt-26r1
…/migrate-to-aedt-26r1 # Conflicts: # tests/system/test_cutout.py
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
7 participants
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.
With AEDT 2026.1 now installed on our self-hosted runners, this PR is updating the
ci-pr.ymlandci-release.ymlworkflow files to make use of that version forpyedb's CI.Additionally, references to 2025.2 have been updated to 2026.1 in the documentation files and in the examples contained within the docstrings of various scripts.
This migration is somewhat tricky given that a dev version of the
ansys-edb-corepackage is currently needed in order to use AEDT version 2026.1 withpyedb.The suggested approach does not update the version of this package in
pyproject.toml, but upgrades it to the required dev version directly within the CI jobs that need it.This is, of course, open to discussion.
This approach is imperfect, given that a
pyedbuser trying to use 2026.1 would currently encounter problems when installing the stable release ofansys-edb-coreas listed in thepyproject.toml. But on the other hand, it may be preferable, for the time being, to restrict usage of 2026.1 to the CI only, given the adjustments that currently need to be made to the default AEDT installation in order to use 2026.1 withpyedb.This PR also enables grpc flag set as
Truefor the first time to be aligned with PyAEDT v1.0 release.Due to compatibility issues we were forced using ansys-edb-core v0.2.6 instead of 0.3.0 due to instabilities with grpc n Linux. Some tests from CICD has been skipped based on ansys-edb-core==0.2.6 version so when we migrate to 0.3.0 those ones will be triggered again. This is a temporary solution waiting the next Service pack which will resolves these issues.