-
Notifications
You must be signed in to change notification settings - Fork 653
Add periodic jobs for E2E conformance tests #107
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
Add periodic jobs for E2E conformance tests #107
Conversation
- test against kubernetes master - test against kubernetes latest release(v1.10.0) Closes #103
|
/ok-to-test |
|
Current supported trigger comments, we can rerun the failed test jobs with specific comments. |
.zuul.yaml
Outdated
| - cloud-provider-openstack-acceptance-test-keystone-authentication-authorization | ||
| - cloud-provider-openstack-acceptance-test-lb-octavia | ||
| - cloud-provider-openstack-acceptance-test-e2e-conformance | ||
| - cloud-provider-openstack-acceptance-test-e2e-conformance-latest-release |
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.
can we rename latest-release to stable-branch-1.10 please?
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.
That means we have to update this yaml file every time when we release a new branch ?
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.
@dims , of course, stable-branch-1.10 is more exact, thank you.
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.
@dixudx over time we will accumulate 3 of these (just like k8s supports 3 last branches) and we will have to drop the oldest one when we go beyond 3
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.
@dixudx yes, if we use explicit version job name, we have to update .zuul.yaml when k8s release; if we use current name, we only need to update OpenLab zuul job define.
|
Zuul encountered a syntax error while parsing its configuration in the Job cloud-provider-openstack-acceptance-test-e2e-conformance-latest-release not defined The error appears in the following project or project-template stanza: project: in "kubernetes/cloud-provider-openstack/.zuul.yaml@master", line 1, column 3 |
|
Build failed.
|
|
/test cloud-provider-openstack-e2e-conformance |
|
Build succeeded.
|
|
Ready to go |
|
/approve |
|
/test all |
|
/test cloud-provider-openstack-all |
|
/retest |
|
/test all |
|
Build failed.
|
|
/test all |
|
Build failed.
|
|
/test all |
|
Build succeeded.
|
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims 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 |
Add periodic jobs for E2E conformance tests
What this PR does / why we need it:
Add periodic jobs for E2E conformance tests
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #103Special notes for your reviewer:
@dims
Release note: