Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix CI builds and rework testing harness #419

Merged
merged 2 commits into from
Jun 6, 2024
Merged

fix CI builds and rework testing harness #419

merged 2 commits into from
Jun 6, 2024

Conversation

maxhoesel
Copy link
Collaborator

No description provided.

After yet another breaking package update
(docker/docker-py#3257),
its high time we permanently pin all development packages
*and their dependencies* to a known.-good version.
pip-tools lets us do that without losing the simple requirements.txt
file that allows easy installation, so lets use that.
a little while ago, we were starting to get "imp" import errors
in CI builds, which I initially were assumed to be from pytest.
In fact, it was the pytest-virtualenv package that we used
to generate a virtualenv with a specific ansible version for tests.

As there is no easy replacement for this package, and the package
itself is stale (no release in 5 years), the testing harness now just
installs the desired version of ansible-core straight into the main
devel virtualenv. This is a bit ugly as it could interfere with other
user tasks, but it leaves the interface the same and helps simplify the test fixture code.
Said code also now reliably isolates tes environments from another and the user-wide collections.

Combined with package pinning introduced in the previous commit,
we should no longer have CI failures due to packages or their deps
updating and breaking things.
@maxhoesel maxhoesel added the chore Backend change that doesn't affect users label Jun 6, 2024
@maxhoesel maxhoesel merged commit 1fb2bd0 into main Jun 6, 2024
7 checks passed
@maxhoesel maxhoesel deleted the pip-compile branch June 6, 2024 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Backend change that doesn't affect users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant