kubevirtci
kubevirtci copied to clipboard
kubevirt
automate centos version bump
#1085 was necessary because the pinned centos version vanished. Therefore we should implement an automated bump.
Originally posted by @brianmcarey in https://github.com/kubevirt/kubevirtci/pull/1085#pullrequestreview-1643647368
we discussed it also offline, better to see if it happens again and again it will be better to not bump it too much otherwise, so we will have less moving pieces
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
we can see it happens just once in few months, i am against updating it every day, posted comments on the PR with reasons
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
This should be handled by https://github.com/kubevirt/project-infra/commit/5ec71d62fab85ee0db8ddcad5b9418ad0f279213
/close
@brianmcarey: Closing this issue.
In response to this:
This should be handled by https://github.com/kubevirt/project-infra/commit/5ec71d62fab85ee0db8ddcad5b9418ad0f279213
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.