Remove old TravisCI config file

[asherf]

As far as I can tell, TravisCI is no longer used in this repo.

Feel free to close this PR if travisCI is still being used and this file should remain

[k8s-ci-robot]

Welcome @asherf!

It looks like this is your first PR to kubernetes-sigs/aws-efs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-efs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @asherf. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[asherf]

@mskanth972 @Ashley-wenyizha ping

[kuba-wolf]

Note: FSx for Lustre did this as well in this PR: kubernetes-sigs/aws-fsx-csi-driver#302. @asherf you should also remove the test coverage check in the readme: https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/docs/README.md?plain=1#L1

[kuba-wolf]

@asherf Sorry for taking so long to come back to this, can you rebase those 3 commits into one? Once that's done I can help this get merged.
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: asherf
Once this PR has been reviewed and has the lgtm label, please assign nckturner for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[asherf]

@asherf Sorry for taking so long to come back to this, can you rebase those 3 commits into one? Once that's done I can help this get merged. /ok-to-test

done.

[kuba-wolf]

Can you squash the 4 commits into one?

[asherf]

Can you squash the 4 commits into one?

you can do a squash commit in GH when you land the PR.
I don't have this branch locally on my computer anymore.

[kuba-wolf]

afaik the preferred approach for reviews is to have the cli bot perform the merge, part of the reason being that an admin for the repo is needed to merge the pr in this way. I hope you don't mind, I rebased your commit for you and opened a new PR: #1129