Skip to content
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

Merged
merged 1 commit into from
Dec 4, 2018

Conversation

pohly
Copy link
Contributor

@pohly pohly commented Dec 3, 2018

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

@k8s-ci-robot
Copy link
Contributor

Welcome @pohly! It looks like this is your first PR to kubernetes/test-infra 🎉🎉

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/config Issues or PRs related to code in /config labels Dec 3, 2018
@pohly pohly force-pushed the sig-storage-csi-lib-utils branch from f0afd49 to 4c6eded Compare December 3, 2018 16:02
@pohly
Copy link
Contributor Author

pohly commented Dec 3, 2018

/cc @msau42 @saad-ali

If there's a way to test this config fragment before merging, the please let me know - as it stands, it's basically completely untested.

make test in the repo under test of course passes.

presubmits:
github.com/kubernetes-csi/csi-lib-utils:
- name: pull-sig-storage-csi-lib-utils
always_run: true
Copy link
Member

@krzyzacy krzyzacy Dec 3, 2018

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

Copy link
Contributor Author

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.

Copy link
Member

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

@krzyzacy
Copy link
Member

krzyzacy commented Dec 3, 2018

@pohly
Copy link
Contributor Author

pohly commented Dec 3, 2018

@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 gcr.io/k8s-testimages/kubekins-e2e:v20181129-33929460d-master image and it's ./hack/ci/build-all.sh script. But you were just using that as an example for something that uses podutils and not suggesting that I switch to that image, right?

@pohly
Copy link
Contributor Author

pohly commented Dec 3, 2018

@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:
Copy link
Member

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"

Copy link
Contributor Author

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?

Copy link
Member

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).

@pohly pohly force-pushed the sig-storage-csi-lib-utils branch from 4c6eded to 7531f85 Compare December 4, 2018 15:50
@pohly
Copy link
Contributor Author

pohly commented Dec 4, 2018

@msau42 @krzyzacy updated, please have another look.

@krzyzacy
Copy link
Member

krzyzacy commented Dec 4, 2018

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)

@pohly
Copy link
Contributor Author

pohly commented Dec 4, 2018 via email

@krzyzacy
Copy link
Member

krzyzacy commented Dec 4, 2018

@pohly sorry, missed that 😂 For some reason I read it as a brand new org, nvm

edit: and yes, please add

kubernetes-csi/csi-lib-utils:
- trigger

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
@pohly pohly force-pushed the sig-storage-csi-lib-utils branch from 7531f85 to 21b20c3 Compare December 4, 2018 19:45
@pohly
Copy link
Contributor Author

pohly commented Dec 4, 2018

@krzyzacy I've added the "trigger" plugin.

@k8s-ci-robot k8s-ci-robot added the area/prow Issues or PRs related to prow label Dec 4, 2018
@msau42
Copy link
Member

msau42 commented Dec 4, 2018

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 4, 2018
@k8s-ci-robot
Copy link
Contributor

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
Copy link
Member

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

Copy link
Contributor Author

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.

Copy link
Member

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.

@krzyzacy
Copy link
Member

krzyzacy commented Dec 4, 2018

/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2018
@k8s-ci-robot k8s-ci-robot merged commit 3085040 into kubernetes:master Dec 4, 2018
@k8s-ci-robot
Copy link
Contributor

@pohly: Updated the following 2 configmaps:

  • job-config configmap using the following files:
    • key csi-lib-utils-config.yaml using file config/jobs/kubernetes-csi/csi-lib-utils/csi-lib-utils-config.yaml
  • plugins configmap using the following files:
    • key plugins.yaml using file prow/plugins.yaml

In response to this:

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

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.

@pohly
Copy link
Contributor Author

pohly commented Dec 4, 2018

Now that this is merged, should /test pull-sig-storage-csi-lib-utils work right away?

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:
Copy link
Member

@krzyzacy krzyzacy Dec 4, 2018

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)

Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/prow Issues or PRs related to prow cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants