-
Notifications
You must be signed in to change notification settings - Fork 814
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
Test integration with prow #162
Test integration with prow #162
Conversation
Hi @kschumy. Thanks for your PR. I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/hold |
/ok-to-test |
f1a725f
to
d7f1c8f
Compare
/lgtm Thanks! /cc @leakingtapan This will let you specify your own VPC when run locally. If not configured, it will use the default VPC ID, pre-created in our test account. |
will create a new VPC in your AWS account, and delete on test complete. |
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.
Didn't see prow job is running, is it running yet?
Makefile
Outdated
@@ -41,7 +54,7 @@ test-sanity: | |||
test-integration: | |||
curl -L ${AWS_K8S_TESTER_DOWNLOAD_URL} -o ${AWS_K8S_TESTER_PATH} | |||
chmod +x ${AWS_K8S_TESTER_PATH} | |||
aws-k8s-tester csi test integration --terminate-on-exit=true --csi=master --timeout=20m | |||
aws-k8s-tester csi test integration --terminate-on-exit=true --timeout=20m ${CSI_FLAG} ${VPC_ID_FLAG} |
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.
Should it be ${AWS_K8S_TESTER_PATH} csi test integration --terminate-on-exit=true --timeout=20m ${CSI_FLAG} ${VPC_ID_FLAG}
?
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.
fixed!
@@ -14,6 +14,11 @@ Must satisfy also the requirements for `aws-ebs-csi-driver` | |||
make test-integration | |||
``` | |||
|
|||
#### Overriding Defaults | |||
- The master branch of `aws-ebs-csi-driver` is used by default. To run using a pull request for `aws-ebs-csi-driver`, set `PULL_NUMBER` as an environment variable with a value equal to the pull request number. |
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.
So is it possible to run the integ test against local changes? It feels to me that in local development, test for local changes will be very useful. We don't have to do it here. But want to know what's our thoughts on this?
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.
Yeah it's doable.
- create a PR with your local change
- pass that
PULL_NUMBER
environmental variable tomake test-integration
In the future, we can support specifying git origin and branch name, so we can test it without creating a PR.
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.
- create a PR with your local change
- pass that
PULL_NUMBER
environmental variable tomake test-integration
Confirming this works locally
d7f1c8f
to
1fa6fb4
Compare
/lgtm |
This PR has to be merged first. |
/lgtm Please rebase the commits then I will approve |
1fa6fb4
to
4a6844e
Compare
done! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kschumy, leakingtapan 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 |
Bug 1872244: Update vendor/ directory
Is this a bug fix or adding new feature?
Feature
What is this PR about? / Why do we need it?
See issue #36
make test-integration
uses PULL_NUMBER for prow and a flag for vpc-idWhat testing is done?
Testing locally