Consider re-ordering launch defaults or providing additional launch selectors
sferich888 opened this issue · 4 comments
xref (how image resolution happens today): https://github.com/openshift/ci-chat-bot/blob/master/manager.go#L695-L707 with the current logic; simply X.Y resolutions always prefer / resolve nightly builds, then CI builds then GA releases.
As a user who primary works with 'released' clusters/versions; having the launch command (inputting 4.10) default to deploying a 'nightly' build is frustrating/less than desired (for my use-cases). Thus I would like to see us re-order the defaults (so that GA release are evaluated first; then Nighties then CI builds), however this use-case may be less desirable for other functions/parts of our organization.
Thus I would like to propose that the launch command be alerted take an additional argument that is the release status type of cluster you want to deploy or source your image reference from. Ex: launch 4.10 release|ga or launch 4.10 nightly.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
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 by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./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.