-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
sig-storage: initial config for kubernetes-csi/csi-lib-utils #10309
sig-storage: initial config for kubernetes-csi/csi-lib-utils #10309
Conversation
Welcome @pohly! It looks like this is your first PR to kubernetes/test-infra 🎉🎉 |
f0afd49
to
4c6eded
Compare
presubmits: | ||
github.com/kubernetes-csi/csi-lib-utils: | ||
- name: pull-sig-storage-csi-lib-utils | ||
always_run: true |
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.
you can flip always_run
to false
to start with, and you can trigger it on your repo with /test pull-sig-storage-csi-lib-utils
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.
I had considered that, but as we don't have a lot going on in that repo I wasn't worried about breaking anything by making the testing mandatory right away.
@msau42 your call - we can also keep it disabled and do another PR here once we know that it works.
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.
always_run is fine. i don't expect much activity yet
also create new jobs with pod-utils now :-) it's as easy as https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/kind/kind-presubmits.yaml#L2-L12 and you can drop most of the args |
@krzyzacy Thanks for the pointer to "Create a new job" - when I asked about prow on Slack the other day, I was only pointed to prow's own README.md and existing examples, so I started from those. Your example uses the |
@krzyzacy is the directory structure okay? The org is the "kubernetes-csi" working group inside the "sig-storage" SIG, the repo is "csi-lib-utils" - I wasn't quite sure where to put the config .yaml, so I created a directory for "sig-storage" with a "csi" sub-directory for the CSI specific repos. |
@@ -0,0 +1,5 @@ | |||
approvers: |
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.
I would have the directory structure match the actual github repo structure, so "kubernetes-csi/csi-lib-utils"
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 no "sig-storage", i.e. config/jobs/kubernetes-sigs/kubernetes-csi/csi-lib-utils/csi-lib-utils-config.yaml
and config/jobs/kubernetes-sigs/kubernetes-csi/OWNERS
?
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.
No kubernetes-sigs either (it is an actual GitHub org).
4c6eded
to
7531f85
Compare
if this is a new org, did you configure webhooks? Also you need to add an entry, something like https://github.com/kubernetes/test-infra/blob/master/prow/plugins.yaml#L300-L308 (you can choose what plugins you want to enable) |
Sen Lu <[email protected]> writes:
if this is a new org, did you configure webhooks?
The kubernetes-csi org itself isn't new and has been part of Kubernetes
for a while now, so I think the webhooks are in place. For example, the
PR dashboard shows the PRs in the new repo.
Also you need to add an entry, something like
https://github.com/kubernetes/test-infra/blob/master/prow/plugins.yaml#L300-L308
(you can choose what plugins you want to enable)
Isn't that already covered by the entry for "kubernetes-csi"?
https://github.com/kubernetes/test-infra/blob/f61cf6eab16515ffc32a85489d56847aee9f408a/prow/plugins.yaml#L445-L463
Or is there perhaps some plugin missing? I have no idea what each plugin
does, but looking at the other entries perhaps "trigger" is missing?
In other words, add this?
```
kubernetes-csi/csi-lib-utils:
- trigger
```
|
@pohly sorry, missed that 😂 For some reason I read it as a brand new org, nvm edit: and yes, please add
if that's not present. |
kubernetes-csi/csi-lib-utils is a brand-new stand-alone repo with some Go utility package (one at the moment, more to come). "make test" inside it enforces coding style and that unit tests pass, which is something that we want to ensure before merging any PR. This is the first config for kubernetes-csi, hence the new OWNERS file. Fixes: kubernetes-csi/csi-lib-utils#2
7531f85
to
21b20c3
Compare
@krzyzacy I've added the "trigger" plugin. |
/lgtm |
LGTM label has been added. Git tree hash: fe574c6461b3cf361887bf5ba988cae127b70178
|
containers: | ||
# This image was chosen over the more often used kubekins-e2e because | ||
# it is smaller and has everything we need (basically just a Go environment). | ||
- image: gcr.io/k8s-testimages/gcloud-in-go:v20180927-6b4facbe6 |
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.
if you just need go, you can also choose to use something like golang:1.11.2
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.
I was trying to use something that might have been pulled already, i.e. something which is also used by other jobs. Not sure whether that makes sense?
But I agree, now that all of the special logic is handled by the pod-utils, a generic image should work just as well.
Either way, I'd like to get this merged and perhaps it can be tweaked further later on. We have quite a few repos under kubernetes-csi that might benefit from closer integration with Prow, so I expect that we'll come back to 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.
You might want to control go versions explicitly - feel free to come back and tune this if you are hitting issues.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krzyzacy, msau42, pohly 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 |
@pohly: Updated the following 2 configmaps:
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. |
Now that this is merged, should I tried that in kubernetes-csi/csi-lib-utils#4 (comment) but so far nothing has been triggered, at least nothing is visible in github. |
@@ -0,0 +1,17 @@ | |||
presubmits: | |||
github.com/kubernetes-csi/csi-lib-utils: |
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.
ooooops, drop github.com here 😂 (prow key jobs off org/repo pattern)
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.
Thanks for debugging it. Fix is in #10340.
kubernetes-csi/csi-lib-utils is a brand-new stand-alone repo with some
Go utility package (one at the moment, more to come). "make test"
inside it enforces coding style and that unit tests pass, which is
something that we want to ensure before merging any PR.
This is the first config for sig-storage, hence the new OWNERS file.
Fixes: kubernetes-csi/csi-lib-utils#2