-
Notifications
You must be signed in to change notification settings - Fork 216
USHIFT-5202: Optimize CI runtime for pre-submit jobs to run faster and more balanced #4318
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
USHIFT-5202: Optimize CI runtime for pre-submit jobs to run faster and more balanced #4318
Conversation
@ggiguash: This pull request references USHIFT-5202 which is a valid jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to reviewers: the diff of the following 3 files is misleading by looking like files were moved from bootc to ostree hierarchies. The logic of the change is to delete bootc cos9 osconfig
tests and split ostree rhel osconfig
tests into 3 parts.
/test ? |
@ggiguash: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In 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-sigs/prow repository. |
/test e2e-aws-tests |
@ggiguash: This pull request references USHIFT-5202 which is a valid jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
@ggiguash: This pull request references USHIFT-5202 which is a valid jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
@ggiguash: This pull request references USHIFT-5202 which is a valid jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
@ggiguash: This pull request references USHIFT-5202 which is a valid jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
/test e2e-aws-tests-bootc-periodic-arm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pmtk 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 |
1 similar comment
/test e2e-aws-tests-bootc e2e-aws-tests-bootc-arm e2e-aws-tests-arm |
/test e2e-aws-tests-bootc |
1 similar comment
/test e2e-aws-tests-bootc |
3 similar comments
/retest-required |
/test e2e-aws-tests-bootc |
@ggiguash: 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-sigs/prow repository. I understand the commands that are listed here. |
The goal of this change is to complete the VM creation and test phase under 45m.
The following changes were implemented:
osconfig
tests that take 1.5h were split into 3 parts for ostree, similar to what already exists for bootc.The metal-tests stage now takes around 45m, which is ~15m for creating VMs and ~30m for running tests.