-
Notifications
You must be signed in to change notification settings - Fork 100
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
Add pulp_integration framework #400
Conversation
a81d526
to
4ab8744
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple suggestions, but I don't see anything terribly off-the-rails here for your first GHA experience ;)
Lastest working run against my fork: https://github.com/Shrews/ansible-builder/runs/7201566704?check_suite_focus=true |
Merging, should go green once it has access to local secrets. We may need to retarget the pulp job to only run on maintainer-sourced PRs or merge jobs only so it doesn't fail on all future PRs. |
This adds a new
pulp_integration
test framework that will allow us to have a local image repository that supports signed images. The PR that adds support for container image signature validation (PR #371) will be able to use this to add integration tests.Note that the Pulp Integration job fails in this PR because it is adding a new GHA job that uses a secret. It will not have access to this secret until this is merged, but I verified that it does work as a PR against my own fork, seen here:
https://github.com/Shrews/ansible-builder/runs/7134536766?check_suite_focus=truehttps://github.com/Shrews/ansible-builder/runs/7201566704?check_suite_focus=truehttps://github.com/Shrews/ansible-builder/runs/7254569323?check_suite_focus=true