OSSM-3733: Add istio operator postsubmit jobs#39163
OSSM-3733: Add istio operator postsubmit jobs#39163openshift-merge-robot merged 4 commits intoopenshift:masterfrom
Conversation
Signed-off-by: Yuanlin <yuanlin.xu@redhat.com>
|
@yxun: This pull request references OSSM-3733 which is a valid jira issue. DetailsIn response to this: 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. |
|
@yxun, Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
| -r istio-operator \ | ||
| -b maistra-2.4 \ | ||
| -f /creds-github/token \ | ||
| '-c make clean update-charts-2.1 update-charts-2.2 update-charts-2.3' \ |
There was a problem hiding this comment.
This won't work. Operator 2.2 doesn't know about 2.3 charts.
| -r istio-operator \ | ||
| -b maistra-2.4 \ | ||
| -f /creds-github/token \ | ||
| '-c make clean update-charts-2.1 update-charts-2.2 update-charts-2.3' \ |
There was a problem hiding this comment.
Should you include 2.4 and remove 2.1?
There was a problem hiding this comment.
Do we have a 2.4 operator ready for update charts ?
I can update that.
|
/pj-rehearse |
| memory: 2Gi | ||
| timeout: 20m0s | ||
| workflow: servicemesh-istio-e2e-aws | ||
| - as: update-charts-in-2-4 |
There was a problem hiding this comment.
Actually I don't think we need a 2.4 job.
The whole point of these jobs is to update the latest (i.e., 2.4) charts when previous charts change. Since 2.4 is the latest, it doesn't make sense for it to exist.
|
/pj-rehearse |
1 similar comment
|
/pj-rehearse |
|
LGTM. Add the post submit true and I'll approve it |
|
/retest |
|
/pj-rehearse ack |
|
[REHEARSALNOTIFIER] Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jwendell, yxun The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@yxun: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@yxun: Updated the following 2 configmaps:
DetailsIn response to this: 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. |
No description provided.