-
Notifications
You must be signed in to change notification settings - Fork 14
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: updates GitHub Actions runner image and restart policy #255
Conversation
The newest version of the runner has podman v4 which is needed for compatibilty with the version of docker
Restarting trestlebot containers cfreate unexpected behavior because of the shared volume. For this use case, it should be never. Signed-off-by: Jennifer Power <[email protected]>
Signed-off-by: Jennifer Power <[email protected]>
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.
Questions on usage of logging in exception handlers.
try: | ||
clean(tmpdir, repo) | ||
except Exception as e: | ||
logging.error(f"Failed to clean up temporary git repository: {e}") |
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.
@jpower432 should this use a logger
instance vs logging?
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.
Thanks for pointing this out. I think the logging statement should be removed here. It was left in for temporary debugging for an issue that this change resolves.
The logging statement was for debugging and should be removed to ensure resource cleanup errors are properly logged Signed-off-by: Jennifer Power <[email protected]>
@gvauter PTAL |
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.
LGTM
Description
Changes
podman
which is compatible with version of Docker (Note - this public beta slated to go GA in Sept)Rationale
Why use
podman
anddocker
?They are used in different contexts.
podman
is used to manage containers in E2E testing.docker
GitHub Actions are used for image building in the release pipeline.podman
pods is required to run the mock server and trestle-bot on the same network stack. It is also what the team is more familiar with.image
building in GitHub Actions, thedocker
actions have the features we need for image tag management and caching.Alternatives
ubuntu-latest
. This is possible through brew or manually, but we would need to back out the changes in Sept.Fixes #251
Type of change
How has this been tested?
Checklist