-
Notifications
You must be signed in to change notification settings - Fork 40
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
Enable periodic task execution for OAI End-to-End testing #234
Enable periodic task execution for OAI End-to-End testing #234
Conversation
Signed-off-by: Victor Morales <v.morales@samsung.com>
@electrocucaracha What is the benefit of doing this? Sorry I am not aware why are we doing this? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: radoslawc 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 |
This will execute the OAI end-to-end tests on a daily basis |
Co-authored-by: Rado Chmiel <r.chmiel@partner.samsung.com>
/lgtm |
@electrocucaracha: Updated the
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/test-infra repository. |
…ject#234) * Enable OAI periodic End-to-End execution Signed-off-by: Victor Morales <v.morales@samsung.com> * Update schedule timeframe Co-authored-by: Rado Chmiel <r.chmiel@partner.samsung.com> --------- Signed-off-by: Victor Morales <v.morales@samsung.com> Co-authored-by: Rado Chmiel <r.chmiel@partner.samsung.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
Until now, OAI e2e execution is done on demand basis. That restriction limits the capability for catching errors on new changes. This change enables the End-to-End test execution for OAI use case.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: