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

chore: Remove forceful cleanup of all containers #1317

Merged

Conversation

Venefilyn
Copy link
Member

@Venefilyn Venefilyn commented Jul 23, 2024

A while back it was introduced to cleanup the containers due to caching
issue. This also cleans up your own containers and should not be ran
locally whatsoever as it forcefully removes all containers.

This is just a removal for now. It is better to have to run the command
twice than have to deal with the aftermath of all your own containers
suddenly being gone.

Introduced in #295

Jira Issues:

Checklist

  • PR has been tested manually in a VM (either author or reviewer)
  • Jira issue has been made public if possible
  • [RHELC-] or [HMS-] is part of the PR title
  • GitHub label has been added to help with Release notes
  • PR title explains the change from the user's point of view
  • Code and tests are documented properly
  • The commits are squashed to as few commits as possible (without losing data)
  • When merged: Jira issue has been updated to Release Pending if relevant

@Venefilyn Venefilyn added skip/changelog If it should be excluded from changelog or Release notes. Such as infra, reverted PRs, etc. tests/skip This PR does not require integration tests to be run. labels Jul 23, 2024
@has-bot
Copy link
Member

has-bot commented Jul 23, 2024

This PR does not require integration tests to be run.


Comment generated by an automation.

Copy link

codecov bot commented Jul 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.84%. Comparing base (00c404b) to head (dc14294).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1317   +/-   ##
=======================================
  Coverage   95.84%   95.84%           
=======================================
  Files          55       55           
  Lines        4771     4771           
  Branches      840      840           
=======================================
  Hits         4573     4573           
  Misses        112      112           
  Partials       86       86           
Flag Coverage Δ
centos-linux-7 91.05% <ø> (ø)
centos-linux-8 91.98% <ø> (ø)
centos-linux-9 92.02% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

A while back it was introduced to cleanup the containers due to caching
issue. This also cleans up your own containers and should not be ran
locally whatsoever as it forcefully removes all containers.

This is just a removal for now. It is better to have to run the command
twice than have to deal with the aftermath of all your own containers
suddenly being gone.
@Venefilyn Venefilyn force-pushed the chore/remove-forceful-container-removal branch from a3d4fd2 to dc14294 Compare July 23, 2024 15:18
Copy link
Contributor

@pr-watson pr-watson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@Venefilyn Venefilyn merged commit 601ce2c into oamg:main Jul 24, 2024
18 checks passed
@Venefilyn Venefilyn deleted the chore/remove-forceful-container-removal branch July 24, 2024 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip/changelog If it should be excluded from changelog or Release notes. Such as infra, reverted PRs, etc. tests/skip This PR does not require integration tests to be run.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants