-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[redhat-developer/odo] Remove periodic runs using the aws
cluster profile
#44645
[redhat-developer/odo] Remove periodic runs using the aws
cluster profile
#44645
Conversation
aws
cluster profile
885fc66
to
6ac50fd
Compare
We are asked to move away from using the `aws` cluster profile. As depicted in [1] and as discussed in our community calls, it makes sense for odo to remove our periodic Prow runs (the ones that were using the `aws` cluster profile) as they don't seem to be that useful anyway. We already have good coverage with the checks that we run on IBM Cloud. [1] redhat-developer/odo#7111 Signed-off-by: Armel Soro <asoro@redhat.com>
Signed-off-by: Armel Soro <asoro@redhat.com>
6ac50fd
to
3771047
Compare
[REHEARSALNOTIFIER] Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@rm3l: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kadel, rm3l The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes redhat-developer/odo#7111
We are asked to move away from using the
aws
cluster profile.As depicted in [1] and as discussed in our community call, it makes sense for
odo
to remove our periodic Prow runs (the ones that were using theaws
cluster profile) as they don't seem to be that useful anyway.We already have good coverage with the checks that we run on IBM Cloud.
NOTE: only the periodic runs using the
aws
cluster profile are being removed, not the ones using theaws-cspi-qe
cluster profile (which are used for interop tests and managed by a different team).[1] redhat-developer/odo#7111